issue-progress-tracking
/issue-progress-tracking
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.
- Author
- yonatangross ↗
- Repository
- orchestkit ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author 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.
How it works
- Invocation
- Phase 1: Start Work
- Phase 2: During Work — Small Commits
- Phase 3: Report Progress (Long Implementations)
- Phase 4: Complete Work
- Rules Quick Reference
- Key Decisions
- Common Mistakes
- Related Skills
SKILL.md preview
---
name: issue-progress-tracking
license: MIT
compatibility: "Claude Code 2.1.277+."
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
user-invocable: false
disable-model-invocation: true
allowed-tools: "Bash"
effort: low
model: haiku
metadata:
category: workflow-automation
version: "1.0.0"
author: "OrchestKit"
complexity: "low"
tags: "git, github, issues, tracking, workflow"
---
# 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:
```text
${CLAUDE_PLUGIN_ROOT}/skills/issue-progress-tracking/SKILL.md
```
---
## Phase 1: Start Work
Label the issue and create a feature branch:
```bash
# Move issue to in-progress
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."
# Create feature branch
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:
```bash
# Each commit references the issue number
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:
```bash
gh issue comment $ARGUMENTS[0] --body "Progress update:
- Completed: database schema, API endpoints
- In progress: frontend components
- Remaining: tests, documentation"
```
**When to post updates:**
- After completing a major milestone
- When blocked or changing approach
- Before stepping away from a long task
---
## Phase 4: Complete Work
Create the PR and update labels:
```bash
# Create PR that closes the issue
gh pr create \
--title "feat(#$ARGUMENTS[0]): brief description" \
--body "Closes #$ARGUMENTS[0]
## Changes
- Change 1
- Change 2
## Test Plan
- [ ] Unit tests pass
- [ ] Manual verification"
# Update issue status
gh issue edit $ARGUMENTS[0] --add-label "status:in-review" --remove-label "status:in-progress"
```
---
## Rules Quick Reference
| Rule | Impact | What It Covers |
|------|--------|----------------|
| [Start Work Ceremony](rules/start-work-ceremony.md) | HIGH | Branch creation, label updates, initial comment |
| [Small Commits](rules/small-commits.md) | HIGH | Atomic commits referencing issues |
**Total: 2 rules across 2 categories**
---
## Key Decisions
| Decision | Choice | Rationale |
|----------|--------|-----------|
| Label prefix | `status:` | Consistent with GitHub conventions |
| Branch format | `issue/<N>-desc` | Links branch to issue automatically |
| Commit reference | `type(#N):` | Conventional commits + issue linking |
| Progress comments | Manual | Keeps humans in the loop |
---
## Common Mistakes
1. **Starting work without labeling** — team loses visibility into who is working on what
2. **Giant commits at the end** — makes review harder and history useless for bisect
3. **Forgetting to link PR to issue** — issue stays open after merge
4. **Not updating labels on PR creation** — issue shows "in-progress" during review
5. **Closing issues manually with `gh issue close`** — issues are closed ONLY by merging a PR with `Closes #N` in the body. During work, comment progress with `gh issue comment`; never close directly.
---
## Related Skills
- `ork:commit` — Commit with conventional format
- `ork:fix-issue` — Full issue resolution workflow
- `ork:implement` — Feature implementation with parallel agents
- `ork:create-pr` — Create pull requests
Files in this package (5)
- SKILL.md 4 KB
- test-cases.json 3 KB
- rules/_sections.md 1 KB
- rules/small-commits.md 1 KB
- rules/start-work-ceremony.md 1 KB
Versions
The database has no other skills named issue-progress-tracking.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version e4751fa6eb6d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100gh-issues
Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers:… - 100create-github-issue
Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue. - 100address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI. - 100pick-up-issue
This skill should be used when the user asks to "pick up an issue", "work on issue #X", "claim issue", "start working on issue", "take this issue", "I'll work on this", or needs to take ownership of a GitHub issue before starting work. - 100address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI. - 100address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.