-
Notifications
You must be signed in to change notification settings - Fork 1.6k
docs: clarify GitHub Copilot CLI limitation for custom prompts #676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
GitHub Copilot's .github/prompts/*.prompt.md files are only recognized as custom slash commands in IDE extensions (VS Code, JetBrains, Visual Studio). The Copilot CLI does not support them (github/copilot-cli#618). This updates the docs to clarify the limitation and point users to the .github/agents/ workaround. Closes #671 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Greptile OverviewGreptile Summary
Confidence Score: 4/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant U as User
participant D as Docs (commands/supported-tools/migration-guide)
participant IDE as Copilot IDE Extension
participant CLI as Copilot CLI
participant Agents as .github/agents/
U->>D: Reads OpenSpec command/tool docs
D-->>U: `.github/prompts/*.prompt.md` works in IDE extensions only
U->>IDE: Uses `/opsx-*` via `.github/prompts/*.prompt.md`
IDE-->>U: Commands available
U->>CLI: Tries same custom prompts
CLI-->>U: Not supported (per docs)
D-->>U: Workaround: set up custom agents
U->>Agents: Configure `.github/agents/`
Agents-->>CLI: Enables CLI workflow via agents
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3 files reviewed, 1 comment
docs/supported-tools.md
Outdated
| | GitHub Copilot | `.github/skills/` | `.github/prompts/`* | | ||
| | iFlow | `.iflow/skills/` | `.iflow/commands/` | | ||
| | Kilo Code | `.kilocode/skills/` | `.kilocode/workflows/` | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Footnote marker ambiguity
docs/supported-tools.md uses * footnotes for both Codex and GitHub Copilot, but the table marks Copilot’s Commands Location as .github/prompts/* (docs/supported-tools.md:29) while Codex is the earlier *-footnoted row. Many Markdown renderers don’t reliably associate repeated * markers in tables with the intended note, so this can render confusingly (Copilot may appear to reference the Codex home-directory note). Consider using distinct markers (e.g., * and **, or 1/2) to ensure the Copilot CLI limitation note is unambiguous.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Addresses review feedback: the shared `*` marker was ambiguous across Markdown renderers. Now uses `*` for Codex and `**` for Copilot. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary
.github/prompts/*.prompt.mdfiles only work in IDE extensions (VS Code, JetBrains, Visual Studio), not in GitHub Copilot CLI.github/agents/custom agents workaround for CLI usageFiles changed
docs/supported-tools.md— Added footnote explaining the IDE-only limitation with links to the upstream issue and workaround docsdocs/commands.md— Renamed "Copilot" to "Copilot (IDE)" in syntax table; added blockquote note about the CLI limitationdocs/migration-guide.md— Added parenthetical clarification to the legacy file referenceTest plan
Closes #671
🤖 Generated with Claude Code