issue-breakdownTurn a spec, plan, or conversation into a reviewed set of linked GitHub issues, cut as vertical slices with blocking edges, and publish them with gh after approval. Use when the user wants a plan, spec, or requirements list split into issues, wants unmet spec requirements filed, or wants a spec itse
issuesRead, create, edit, close, and label a single GitHub issue with gh, including issue types, sub-issues, blocked-by links, milestones, Projects V2 fields, and issue search. Use when the user wants to file or update one issue, set its type, parent, dependencies, labels, milestone, or project field, or
pr-commentsPull a GitHub PR's unresolved review threads and review summaries into context, triage them, then fix the ones the user picks. Read-only on GitHub.
prPrepare and open a GitHub pull request with gh. Plans commits that follow the repo's convention, drafts a reviewer-ready body (summary as pseudocode, call tree or diff; before/after evidence; merge danger), opens the PR as a draft after approval, and never merges without it. Includes contributing to
releaseCut a manual GitHub release for a single-package repo. Finds the previous tag, proposes a SemVer bump from the public-API diff reconciled with commit messages, drafts a Keep a Changelog entry, opens a release PR, then tags and runs gh release create after approval. Detects release-please, semantic-r
shipShip finished work in one run: commit it, push the branch, and optionally open a ready PR, wait for checks, and merge it. Use when asked to \"commit and push\", \"push this up\", \"send it\", \"ship it\", \"commit, push, open a PR, and merge it\", or to get the current changes onto GitHub. Takes an
triageTriage existing GitHub issues and external PRs with gh. Assigns a category and a state role, checks for duplicates and prior rejections, verifies the claim, and then asks for info, writes an agent brief, or closes with a reason. Also classifies PRs as merge, port, close, or park, applies a stale pol