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.8 KiB
1.8 KiB
description, argument-hint
| description | argument-hint |
|---|---|
| Finish the current task end-to-end with changelog, commit, and push | [instructions] |
Wrap it.
Additional instructions: $ARGUMENTS
Determine context from the conversation history first.
Rules for context detection:
- If the conversation already mentions a GitHub issue or PR, use that existing context.
- If the work came from
/isor/pr, assume the issue or PR context is already known from the conversation and from the analysis work already done. - If there is no GitHub issue or PR in the conversation history, treat this as non-GitHub work.
Unless I explicitly override something in this request, do the following in order:
- Add or update the relevant package changelog entry under
## [Unreleased]using the repo changelog rules. - If this task is tied to a GitHub issue or PR and a final issue or PR comment has not already been posted in this session, draft it in my tone, preview it, and post exactly one final comment.
- Commit only files you changed in this session.
- If this task is tied to exactly one GitHub issue, include
closes #<issue>in the commit message. If it is tied to multiple issues, stop and ask which one to use. If it is not tied to any issue, do not includecloses #orfixes #in the commit message. - Check the current git branch. If it is not
main, stop and ask what to do. Do not push from another branch unless I explicitly say so. - Push the current branch.
Constraints:
- Never stage unrelated files.
- Never use
git add .orgit add -A. - Run required checks before committing if code changed.
- Do not open a PR unless I explicitly ask.
- If this is not GitHub issue or PR work, do not post a GitHub comment.
- If a final issue or PR comment was already posted in this session, do not post another one unless I explicitly ask.