Worklog
tokenbender/agent-guides
Issue-led atomic work logging. An agent skill from tokenbender/agent-guides.
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…
Install Issue Progress Tracking
$ npx skills add yonatangross/orchestkit --skill issue-progress-tracking -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yonatangross/orchestkit issue-progress-tracking --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/issue-progress-tracking .claude/skills/issue-progress-tracking && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "issue-progress-tracking" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/issue-progress-tracking into .claude/skills/issue-progress-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-progress-tracking", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/yonatangross/orchestkit/tree/main/src/skills/issue-progress-trackingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add yonatangross/orchestkit --skill issue-progress-tracking -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yonatangross/orchestkit issue-progress-tracking --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/skills/issue-progress-tracking .agents/skills/issue-progress-tracking && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-progress-tracking" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/issue-progress-tracking into .agents/skills/issue-progress-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-progress-tracking", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yonatangross/orchestkit --skill issue-progress-tracking -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yonatangross/orchestkit issue-progress-tracking --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/skills/issue-progress-tracking .cursor/skills/issue-progress-tracking && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "issue-progress-tracking" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/issue-progress-tracking into .cursor/skills/issue-progress-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-progress-tracking", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/yonatangross/orchestkit.git --path src/skills/issue-progress-tracking--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yonatangross/orchestkit --skill issue-progress-tracking -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yonatangross/orchestkit issue-progress-tracking --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/skills/issue-progress-tracking .gemini/skills/issue-progress-tracking && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "issue-progress-tracking" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/issue-progress-tracking into .gemini/skills/issue-progress-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-progress-tracking", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install yonatangross/orchestkit issue-progress-trackingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add yonatangross/orchestkit --skill issue-progress-tracking -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/skills/issue-progress-tracking .github/skills/issue-progress-tracking && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "issue-progress-tracking" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/issue-progress-tracking into .github/skills/issue-progress-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-progress-tracking", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yonatangross/orchestkit --skill issue-progress-tracking -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yonatangross/orchestkit issue-progress-tracking --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/skills/issue-progress-tracking .opencode/skills/issue-progress-tracking && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "issue-progress-tracking" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/issue-progress-tracking into .opencode/skills/issue-progress-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-progress-tracking", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
issue-progress-tracking- GitHub stars
- 288
- Token cost
- ~1.1k tokens
- SKILL.md length
- 345 words
- Files
- 5
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Works in 4 steps: Start Work → During Work — Small Commits → Report Progress (Long Implementations) → …
- Starting work on an issue
- SKILL.md covers Invocation, Phase 1: Start Work, Phase 2: During Work — Small… and Phase 3: Report Progress (Long…, plus 5 more sections
- Calls gh and git
What it does
Issue Progress Tracking is an agent skill from yonatangross/orchestkit. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `rules/_sections.md`, `rules/small-commits.md` and `rules/start-work-ceremony.md`). Compatibility notes: Claude Code 2.1.277+.
It sits in Productivity & Automation, covering Task management. It works with GitHub. The repository describes itself as: The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install ork for stable (v9.x), or ork-alpha for the v10 line, which ships daily. The licence is MIT.
When your agent uses it
- Starting work on an issue
- Tracking progress
- Completing work with a PR
Example prompts
- “/issue-progress-tracking”
Requirements
- Compatibility (from SKILL.md): Claude Code 2.1.277+.
- Pre-approved tools (allowed-tools): Bash
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1f8d8f3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Claude Code 2.1.277+.
From compatibility in the SKILL.md frontmatter.
Context cost
Issue Progress Tracking loads about 1.1k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 345 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from yonatangross/orchestkit at commit 1f8d8f3, republished under its MIT licence (© yonatangross). 345 words, ~1,120 tokens.
Download SKILL.mdSave it as
.claude/skills/issue-progress-tracking/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- 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.
- allowed-tools
- Bash
- compatibility
- Claude Code 2.1.277+.
- license
- MIT
- context
- inherit
- user-invocable
- false
- disable-model-invocation
- true
- effort
- low
- model
- haiku
- metadata.category
- workflow-automation
- metadata.version
- 1.0.0
- metadata.author
- OrchestKit
- metadata.complexity
- low
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.mdPhase 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-descriptionRules:
- 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
© yonatangross, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files in src/skills/issue-progress-tracking of yonatangross/orchestkit.
- SKILL.md
- rules/_sections.md
- rules/small-commits.md
- rules/start-work-ceremony.md
- test-cases.json
Open the folder on GitHubat commit 1f8d8f3
Compare with similar skills
Issue Progress Tracking next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Issue Progress Tracking this skillyonatangross/orchestkit | 288 | — | ~1.1k | Automated safety check: Notes | MIT | |
| Worklogtokenbender/agent-guides | 367 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| OpenObserve PR Briefopenobserve/openobserve | 22k | — | ~1.8k | Automated safety check: Pass | AGPL-3.0 | |
| Agent Kanban Task Workersaltbo/agent-kanban | 485 | — | ~855 | Automated safety check: Pass | Custom licence | |
| Release Kanban Mdantopolskiy/kanban-md | 223 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Pmcoreyhaines31/makerskills | 844 | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
OpenObserve PR Brief
openobserve/openobserve
Produces a read-only morning brief of your open pull requests across the openobserve GitHub org, with a next step for each and a reminder for idle ones.
Agent Kanban Task Worker
saltbo/agent-kanban
Lets an agent read, claim, update and submit an assigned Agent Kanban task through the Realmroot Toolbox CLI, with progress notes and a review handoff.
Release Kanban Md
antopolskiy/kanban-md
Release kanban-md through its tag-triggered GoReleaser workflow, monitor CI, recover safely from failures, and publish user-facing GitHub release notes.
Pm
coreyhaines31/makerskills
When you want to manage projects across your businesses using a kanban + Eisenhower methodology.
Jira
magnus919/agent-skills
Interact with Atlassian Jira from the terminal: search issues with JQL, view details, create issues, add comments, count matches with fast approximate-count, list projects, discover valid…
More from yonatangross/orchestkit
All 107 skills in this repoAPI Design
yonatangross/orchestkit
API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs.
Architecture Decision Record
yonatangross/orchestkit
ADR templates in the Nygard format with context, decision, consequences, and alternatives.
Audit Full
yonatangross/orchestkit
Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing.
Code Review Playbook
yonatangross/orchestkit
Structured review processes, conventional comments, language-specific checklists, and feedback templates.
Create PR
yonatangross/orchestkit
Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.
Explore
yonatangross/orchestkit
Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.
Related
Works with
Categories
Questions about Issue Progress Tracking
What does Issue Progress Tracking 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…. Issue Progress Tracking is an agent skill from yonatangross/orchestkit. 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.
When should I use Issue Progress Tracking?
Issue Progress Tracking fits situations like: starting work on an issue; tracking progress; completing work with a PR.
How do I install Issue Progress Tracking in Claude Code?
Run `npx skills add yonatangross/orchestkit --skill issue-progress-tracking -a claude-code`. Or copy the skill folder (src/skills/issue-progress-tracking in yonatangross/orchestkit) into .claude/skills/issue-progress-tracking in your project. Claude Code loads it when a task matches its description.
How do I install Issue Progress Tracking in Codex?
Run `npx skills add yonatangross/orchestkit --skill issue-progress-tracking -a codex`. Or copy the skill folder (src/skills/issue-progress-tracking in yonatangross/orchestkit) into .agents/skills/issue-progress-tracking in your project. Codex loads it when a task matches its description.
Can I use Issue Progress Tracking in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yonatangross/orchestkit --skill issue-progress-tracking -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-progress-tracking, .gemini/skills/issue-progress-tracking, .github/skills/issue-progress-tracking and .opencode/skills/issue-progress-tracking in your project.
What does Issue Progress Tracking need to run?
Going by SKILL.md and its folder, Issue Progress Tracking needs the command-line tools its instructions call (gh and git). Its frontmatter pre-approves these tools: Bash. Compatibility (from SKILL.md): Claude Code 2.1.277+..
Does Issue Progress Tracking access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Issue Progress Tracking safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Issue Progress Tracking use?
Issue Progress Tracking is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Issue Progress Tracking use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Issue Progress Tracking?
Skills that share tags, products or a category with Issue Progress Tracking: Worklog (tokenbender/agent-guides, 367 stars), OpenObserve PR Brief (openobserve/openobserve, 22k stars), Agent Kanban Task Worker (saltbo/agent-kanban, 485 stars) and Release Kanban Md (antopolskiy/kanban-md, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue Progress Tracking?
yonatangross (a GitHub user) maintains it in yonatangross/orchestkit, which has 288 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on October 6, 2026.
Source: yonatangross/orchestkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.