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.
- Installs
- 215
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/yonatangross/orchestkit --skill issue-progress-tracking- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads issue-progress-tracking automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
# 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:
# 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:
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:
# 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 | HIGH | Branch creation, label updates, initial comment |
| Small Commits | 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
- Starting work without labeling — team loses visibility into who is working on what
- Giant commits at the end — makes review harder and history useless for bisect
- Forgetting to link PR to issue — issue stays open after merge
- Not updating labels on PR creation — issue shows "in-progress" during review
- Closing issues manually with
gh issue close— issues are closed ONLY by merging a PR withCloses #Nin the body. During work, comment progress withgh issue comment; never close directly.
Related Skills
ork:commit— Commit with conventional formatork:fix-issue— Full issue resolution workflowork:implement— Feature implementation with parallel agentsork:create-pr— Create pull requests
FAQ
What does the issue-progress-tracking skill do?
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 do I install issue-progress-tracking?
Run npx skills add https://github.com/yonatangross/orchestkit --skill issue-progress-tracking in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/issue-progress-tracking/ (personal) or .claude/skills/issue-progress-tracking/ (project).
Which AI agents can use issue-progress-tracking?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is issue-progress-tracking safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains issue-progress-tracking?
It is published by yonatangross in yonatangross/orchestkit. It has 215 recorded installs.
More from yonatangross/orchestkit
devops-deployment
yonatangross/orchestkit
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
responsive-patterns
yonatangross/orchestkit
Responsive design with Container Queries, fluid typography, cqi/cqb units, subgrid, intrinsic layouts, foldable devices, and mobile-first patterns for React applications. Use when building responsive layouts or container queries.
architecture-decision-record
yonatangross/orchestkit
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
ui-components
yonatangross/orchestkit
UI component library patterns for shadcn/ui and Radix Primitives. Use when building accessible component libraries, customizing shadcn components, using Radix unstyled primitives, or creating design system foundations.
rag-retrieval
yonatangross/orchestkit
Retrieval-Augmented Generation patterns for grounded LLM responses. Use when building RAG pipelines, embedding documents, implementing hybrid search, contextual retrieval, HyDE, agentic RAG, multimodal RAG, query decomposition, reranking, or pgvector search.
zustand-patterns
yonatangross/orchestkit
Reference for Zustand 5.x state management including slices, middleware, Immer, useShallow, persistence, selectors, and devtools integration. Documents 7 core patterns with TypeScript examples and anti-patterns. Use when building React state management with Zustand instead of Redux.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.