| name | work |
| description | Work on a GitHub issue (implement, test, commit, PR) |
| argument-hint | <issue-number> |
| disable-model-invocation | true |
Work on Issue
Implement a GitHub issue: research, implement, review, commit, PR.
Git state:
!git status --short; git branch --show-current
Issue number: $ARGUMENTS
Workflow
-
Understand & spawn. In one block: gh issue view <n> --json title,body,labels (labels inform the branch type) and the gated explore-issue spawn — a minimal prompt that identifies its role and instructs it to reply "ready" and stop, using no tools. (Spawn-form and resume-form system prompts differ, so an agent's first continue always breaks the prompt cache; gating pays that break at ~0 context and makes every later follow-up a cache hit. Cache TTL is 1h, so pauses for judgment or user questions under an hour don't lose the prefix.) Briefly summarize description, acceptance criteria, and out-of-scope.
-
Task the explorer, then branch while it works. When "ready" arrives, SendMessage the real task immediately: the issue body plus the report format from step 3. While it researches: git fetch origin main, then git checkout -b <type>/<n>-<slug> origin/main (types: feat/fix/refactor/docs/chore) — if the branch already exists, ask: resume it, rebase onto , or use a different name — and read .
