Menu
Use when labeling GitHub issues or triaging the backlog. Applies the project's label taxonomy from docs/labels.md.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use when checking Buildkite CI/CD builds, investigating failures, viewing job logs, or answering questions about pipeline status.
Write a handoff brief summarizing the current conversation so a fresh agent can pick up the work. Writes to a file if given, otherwise copies to the clipboard.
Use when bootstrapping hk pre-commit hooks for a project.
Use when adding, updating, troubleshooting, or managing mise tool dependencies. Supplements /install with mise-specific context about backends, lockfiles, and the github-first policy.
Add a tool pattern to the global Claude Code permissions allow list in bin/sync-claude-settings
Morning update routine: merge Renovate PRs, rebase local work, apply chezmoi changes
Based on SOC occupation classification
| name | label-issue |
| description | Use when labeling GitHub issues or triaging the backlog. Applies the project's label taxonomy from docs/labels.md. |
| argument-hint | [#123 | #123 #456 | all | unlabeled] |
| model | sonnet |
| allowed-tools | ["Read","Bash(gh issue list:*)","Bash(gh issue view:*)","Bash(gh label list:*)"] |
Apply labels to GitHub issues per the taxonomy in docs/labels.md.
local /label-issue
Read @docs/labels.md for the full taxonomy. Quick summary:
| Group | Labels |
|---|---|
| Priority (pick one) | p0:now, p1:soon, p2:later, p3:someday |
| Readiness (pick one) | for:agent, for:human |
| Area (pick one) | area:claude, area:tmux, area:nvim, area:shell, area:git, area:mise, area:renovate, area:os |
| Type (optional) | type:feature, type:bug, type:chore, type:workflow, type:security, type:test |
| Status (optional) | blocked |
Parse arguments to decide what to label:
#123, #456) — label those specific issuesall — triage all open issuesunlabeled — find and triage open issues missing labelsunlabeled# Specific issues
gh issue view 123 --json number,title,body,labels
# All open
gh issue list --state open --json number,title,labels --limit 200
# Unlabeled (filter client-side)
gh issue list --state open --json number,title,body,labels --limit 200
# then filter to issues missing priority OR readiness OR area labels
For each issue, determine:
p0:now)? Wanted soon (p1:soon)? Backlog (p2:later)? Wishlist (p3:someday)?for:agent)? Or does it need human judgment, hardware access, or interactive work (for:human)?claude(statusline): → area:claude, tmux: → area:tmux).type:feature, broken things → type:bug, etc.For each issue, show the proposed labels in a table:
| # | Title | Priority | Readiness | Area | Type |
When labeling specific issues (1-3), apply immediately after showing the table.
When labeling all or unlabeled, present the full table first and wait for user confirmation before applying.
gh issue edit 123 --add-label "p2:later" --add-label "for:agent" --add-label "area:claude" --add-label "type:feature"
Do NOT remove existing valid labels. Only add missing ones.
Report what was labeled:
/label-issue #203 → label one issue
/label-issue #199 #200 #201 → label specific issues
/label-issue unlabeled → find and triage unlabeled issues
/label-issue all → review and label all open issues
/label-issue → same as unlabeled