Feature Request: Add output-style option to slash commands

Resolved 💬 4 comments Opened Dec 20, 2025 by atournayre Closed Feb 14, 2026

Feature Request

Problem

Currently, slash commands cannot be associated with a specific output style. Users must manually switch output styles after invoking a command, which adds friction to the workflow.

Proposed Solution

Add an optional output-style property to the slash command frontmatter:

---
description: Analyze code structure
output-style: bullet-points
---

Analyze the following code and provide insights...

Available styles

  • ultra-concise
  • bullet-points
  • markdown-focused
  • table-based
  • yaml-structured
  • html-structured

Use Cases

  • /commit → ultra-concise (just the commit message)
  • /review → markdown-focused for detailed code reviews
  • /debug → bullet-points for quick scanning
  • /explain → table-based for structured comparisons

Benefits

  • Reduces manual steps in workflows
  • Ensures consistent output for specific tasks
  • Improves plugin/skill UX by allowing authors to define optimal output formats

Additional Context

Output styles are already supported via hooks/settings. This feature would simply allow slash commands to specify their preferred style declaratively in the frontmatter.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗