About

Imported from yonatangross/orchestkit (src/skills/issue-progress-tracking/SKILL.md). Install upstream with npx skills add yonatangross/orchestkit --skill issue-progress-tracking. Copyright stays with the author (MIT).

Issue Progress Tracking

Name: issue-progress-tracking
Author: yonatangross

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 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

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/yonatangross-orchestkit-issue-progress-tracking/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

yonatangross-orchestkit-issue-progress-tracking.ocm.jsonjson

{
  "ocm": "1",
  "id": "yonatangross-orchestkit-issue-progress-tracking",
  "kind": "skill",
  "name": "issue-progress-tracking",
  "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.",
  "publisher": "yonatangross",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "git",
      "github",
      "issues",
      "tracking",
      "workflow",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "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."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/yonatangross/orchestkit",
      "path": "src/skills/issue-progress-tracking/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/yonatangross/orchestkit/blob/HEAD/src/skills/issue-progress-tracking/SKILL.md",
      "key": "yonatangross/orchestkit/src/skills/issue-progress-tracking/SKILL.md"
    },
    "compatibility": "Claude Code 2.1.251+.",
    "allowed_tools": [
      "Bash"
    ],
    "license": "MIT"
  },
  "instructions": "# Issue Progress Tracking\n\nCeremony guide for tracking GitHub issue progress via `gh` CLI. Ensures issues stay updated as work progresses from start to PR.\n\n## Invocation\n\nThis skill is `user-invocable: false` and `disable-model-invocation: true`:\nthere is no `/ork:` form and the model cannot auto-select it (#3313). An agent\nloads it explicitly by Reading this file's path:\n\n```text\n${CLAUDE_PLUGIN_ROOT}/skills/issue-progress-tracking/SKILL.md\n```\n\n---\n\n## Phase 1: Start Work\n\nLabel the issue and create a feature branch:\n\n```bash\n# Move issue to in-progress\ngh issue edit $ARGUMENTS[0] --add-lab",
  "cost": {
    "context_tokens": 940
  }
}

Fetch it by URL: GET /api/v1/registry/yonatangross-orchestkit-issue-progress-tracking/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.