| name | issue-progress-tracking |
| license | MIT |
| compatibility | Claude Code 2.1.220+. |
| description | GitHub issue workflow ceremony using gh CLI — labels issues as in-progress, creates feature branches (issue/N-description), commits with issue references, posts progress comments, and links PRs with Closes #N. Keeps issues in sync with development work. Use when starting work on an issue, tracking progress, or completing work with a PR. |
| context | inherit |
| version | 1.0.0 |
| author | OrchestKit |
| tags | ["git","github","issues","tracking","workflow"] |
| user-invocable | false |
| disable-model-invocation | true |
| allowed-tools | ["Bash"] |
| complexity | low |
| persuasion-type | discipline |
| effort | low |
| model | haiku |
| metadata | {"category":"workflow-automation"} |
Issue Progress Tracking
Ceremony guide for tracking GitHub issue progress via gh CLI. Ensures issues stay updated as work progresses from start to PR.
Invocation
This skill is user-invocable: false and disable-model-invocation: true:
there is no /ork: form and the model cannot auto-select it (#3313). An agent
loads it explicitly by Reading this file's path:
${CLAUDE_PLUGIN_ROOT}/skills/issue-progress-tracking/SKILL.md
Phase 1: Start Work
Label the issue and create a feature branch:
gh issue edit $ARGUMENTS[0] --add-label "status:in-progress" --remove-label "status:todo"
gh issue comment $ARGUMENTS[0] --body "Starting work on this issue."
git checkout -b issue/$ARGUMENTS[0]-brief-description
Rules:
- Always branch from the default branch (main/dev)
- Branch name format:
issue/<number>-<brief-description>
- Never work directly on main/dev
Phase 2: During Work — Small Commits
Commit after each logical step, not at the end. Every commit references the issue:
git commit -m "feat(#$ARGUMENTS[0]): add user model
Co-Authored-By: Claude <noreply@anthropic.com>"
Rules:
- One logical change per commit (atomic)
- Reference issue in every commit:
type(#N): description
- Commit early and often — don't accumulate a massive diff
Phase 3: Report Progress (Long Implementations)
For multi-step work, post progress updates:
gh issue comment $ARGUMENTS[0] --body "Progress update:
- Completed: database schema, API endpoints
- In progress: frontend components
- Remaining: tests, documentation"
When to post updates:
