hatch3r-cli-gh

<!-- HATCH3R-CLI-SKILL-GENERATED v1 --> # gh GitHub CLI — repos, issues, PRs, releases, gists ## §0 — Ambiguity & Safety Gate (P8 B1) Before invoking `gh`, resolve these via `agents/shared/user-question-protocol.md` (default behavior, not exception-driven): - **Scope:** when the target repo/PR/issue number is not explicit (e.g. "close the PR" with several open), confirm which one before acting — never guess the number. - **Irreversibility:** `gh pr close`, `gh pr merge`, `gh release create`, `gh issue close`, `gh repo delete`, and `gh api -X DELETE/POST/PATCH` mutate remote state. Confirm intent before running any of these; they are not safe to assume. - **Ambiguity:** when the request maps to two or more flag combinations with materially different blast radius (e.g. `--squash` vs `--rebase` on `gh pr merge`), ask which one. ## Fan-out Discipline (P8 B2) Tier 1 reference card — no fan-out. This skill is a single-tool usage reference an agent consults inline; it spawns no sub-agents. Fan-out is owned by the calling workflow per its own Fan-out Discipline block. Source: `rules/hatch3r-fan-out-discipline.md` (P8 B2). ## When to Use Reach for `gh` when the task is in the **forge** category and the agent would otherwise call an MCP tool or read large outputs into context. ## Token Cost CLI tools return structured stdout that fits in <1KB for typical queries; equivalent MCP calls regularly exceed 10KB. Reference: Anthropic engineering (Nov 4 2025) — code-execution-over-MCP...