GitHub CLI
This skill is coordination-exempt: skip the ai-coord gate for its declared work.
Routing
Use yeet to author or update a pull request, issue, issue comment, or discussion. yeet owns semantic analysis,
repository templates, Paul's writing voice, idempotency, and direct posting. Route repository renames through
repo-rename so GitHub and local continuity change together.
Authority
- Read and inspect without confirmation.
- Execute reversible or ordinary GitHub writes only when the user explicitly requested that outcome.
- Never delete repositories, releases/assets, workflow runs/caches, secrets/variables, keys, codespaces, extensions, or gists.
- Label deletion is the sole destructive exception: show the target repo, exact labels, commands, and issue/PR impact,
then require approval in a subsequent message before
gh label delete ... --yes.
Workflow
-
Resolve the repository explicitly when cwd is ambiguous. Let the first required read-only command validate authentication; run
gh auth statusonly for auth diagnosis. -
Use installed
gh <command> <subcommand> --helpto resolve flags, JSON fields, and command behavior; CLI JSON field names can differ from API fields. Prefer--jsonwith--jqfor structured output. -
Preview broad writes with the repository, exact targets, commands, and issue/PR impact. An already requested ordinary write does not require a second approval.
Notable Flags (gh 2.98+)
gh pr checkout --worktree <path>andgh issue develop --checkout --worktree <path>check out into a linked git worktree instead of switching the current branch.gh search issues --search-type semantic|hybridranks by relevance: issues only, one page, no--sort/--order, not on GitHub Enterprise Server.gh config set api_host <gateway> --host <host>routes that host's API traffic through a gateway; experimental and not a security boundary.--attach '<file>#<alt>'on issue/PR create, edit, and comment uploads images or videos; route those writes throughyeet.
Completion
Complete when command output verifies the requested GitHub data or state. After a write, fetch the resulting resource. On a partial or ambiguous failure, check whether it changed before retrying. Report the verified state and URL or stable identifier; include the concrete error and next action when incomplete, and distinguish an unknown result from a confirmed failure.