Agent skill · operations · yonatangross
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.
Why this skill is useful
Adds specific commands and workflows for managing GitHub issues with the gh CLI that the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. About 3k tokens when loaded. Last updated 2026-08-06. 215 stars on the source repository.
What this skill does
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: --- Phase 1: Start Work Label the issue and create a feature branch: 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: 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: 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: --- 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 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yonatangross/issue-progress-tracking--a6f050