Auto-updates GitHub issues with commit progress. Use when starting work on an issue, tracking progress during implementation, or completing work with a PR.
Automates GitHub issue tracking from start to PR with branch creation, commit linking, and label updates.
/plugin marketplace add yonatangross/orchestkit/plugin install orkl@orchestkitThis skill is limited to using the following tools:
rules/_sections.mdrules/small-commits.mdrules/start-work-ceremony.mdCeremony guide for tracking GitHub issue progress via gh CLI. Ensures issues stay updated as work progresses from start to PR.
/ork:issue-progress-tracking 123
Label the issue and create a feature branch:
# Move issue to in-progress
gh issue edit $ARGUMENTS --add-label "status:in-progress" --remove-label "status:todo"
gh issue comment $ARGUMENTS --body "Starting work on this issue."
# Create feature branch
git checkout -b issue/$ARGUMENTS-brief-description
Rules:
issue/<number>-<brief-description>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): add user model
Co-Authored-By: Claude <noreply@anthropic.com>"
Rules:
type(#N): descriptionFor multi-step work, post progress updates:
gh issue comment $ARGUMENTS --body "Progress update:
- Completed: database schema, API endpoints
- In progress: frontend components
- Remaining: tests, documentation"
When to post updates:
Create the PR and update labels:
# Create PR that closes the issue
gh pr create \
--title "feat(#$ARGUMENTS): brief description" \
--body "Closes #$ARGUMENTS
## Changes
- Change 1
- Change 2
## Test Plan
- [ ] Unit tests pass
- [ ] Manual verification"
# Update issue status
gh issue edit $ARGUMENTS --add-label "status:in-review" --remove-label "status:in-progress"
| 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
| 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 |
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.ork:commit — Commit with conventional formatork:fix-issue — Full issue resolution workflowork:implement — Feature implementation with parallel agentsork:create-pr — Create pull requestsActivates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.