aa25726ebf
* feat(coding-agent,tui): support argument-hint frontmatter in prompt templates Parse argument-hint from prompt template frontmatter and display it in the autocomplete dropdown description, matching Claude Code's convention for custom commands. Frontmatter format: --- description: Code review argument-hint: "[file | #PR | PR-URL]" --- The hint renders in the description column of the autocomplete list: review [file | #PR | PR-URL] — Code review Closes #2761 * docs(coding-agent,tui): add argument-hint documentation, tests, and built-in hints - Document argument-hint frontmatter in prompt-templates.md with <required>/[optional] convention - Add argument-hint to built-in prompts: pr, is, wr - Expand tests: required/optional hints, missing hints, empty hints, special characters - Add changelog entries for coding-agent and tui
1.0 KiB
1.0 KiB
description, argument-hint
| description | argument-hint |
|---|---|
| Analyze GitHub issues (bugs or feature requests) | <issue> |
Analyze GitHub issue(s): $ARGUMENTS
For each issue:
-
Add the
inprogresslabel to the issue via GitHub CLI before analysis starts. If adding the label fails, report that explicitly and continue. -
Read the issue in full, including all comments and linked issues/PRs.
-
Do not trust analysis written in the issue. Independently verify behavior and derive your own analysis from the code and execution path.
-
For bugs:
- Ignore any root cause analysis in the issue (likely wrong)
- Read all related code files in full (no truncation)
- Trace the code path and identify the actual root cause
- Propose a fix
-
For feature requests:
- Do not trust implementation proposals in the issue without verification
- Read all related code files in full (no truncation)
- Propose the most concise implementation approach
- List affected files and changes needed
Do NOT implement unless explicitly asked. Analyze and propose only.