issue-progress-tracking SKILL.md skillA
issue-progress-tracking from yonatangross/orchestkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yonatangross/orchestkit/issue-progress-tracking@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yonatangross/orchestkit
- Path
src/skills/issue-progress-tracking/SKILL.md- Versions recorded
- 8
- Latest version
- v1.0.0, committed Sep 29, 2026
- First version recorded
- Jun 20, 2026
- Size
- 4,504 bytes
- Repository stars
- 299
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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
…Read the whole file at its exact version.
How to install
mdr add yonatangross/orchestkit/issue-progress-tracking@sha256:2a2790ecc86e29c4The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3vt65mklnki652t2)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between Jun 20, 2026 and Sep 29, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-09-29 | 105a980 | 4,504 B | A | view · diff |
| v1.0.0 | 2026-09-28 | 220adb4 | 4,504 B | A | view · diff |
| v1.0.0 | 2026-09-20 | 02cb935 | 4,518 B | A | view · diff |
| v1.0.0 | 2026-08-29 | 2aed0b0 | 4,518 B | A | view · diff |
| v1.0.0 | 2026-08-11 | f8c256d | 4,518 B | A | view · diff |
| v1.0.0 | 2026-07-25 | 47b78fb | 4,285 B | A | view · diff |
| v1.0.0 | 2026-07-10 | 10a2d30 | 4,285 B | A | view · diff |
| v1.0.0 | 2026-06-20 | 5700399 | 4,285 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4504 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yonatangross/orchestkit · 299 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3vt65mklnki652t2 GET https://markdownregistry.com/api/v1/resolve?ref=yonatangross/orchestkit/issue-progress-tracking GET https://markdownregistry.com/api/v1/blob/2a2790ecc86e29c437ac8ea8daac2cb9875af0da4884b30f9b4678a0bf89bcf4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from yonatangross/orchestkit
Every file in yonatangross/orchestkit