github-clilisted

# GitHub CLI Safety-first wrapper for GitHub CLI (`gh`). Every command is classified by risk level before execution. ## When to Use - User asks to create, list, merge, or close PRs - User asks to manage issues, releases, or repos - User asks to check CI/CD status or workflow runs - User asks to call the GitHub API via `gh api` - User asks to manage GitHub Actions secrets or variables ## Prerequisites 1. **Install:** `brew install gh` or see https://cli.github.com 2. **Auth:** `gh auth login` 3. **Verify:** `gh --version` (requires v2.86+) 4. **Scopes:** `gh auth status` — confirm `repo`, `read:org` scopes minimum ## Safety Model Every `gh` command falls into one of four risk tiers: | Tier | Action Required | Examples | |------|----------------|----------| | **Safe** | Execute immediately | `gh pr list`, `gh issue view`, `gh repo view` | | **Write** | Inform user, then execute | `gh pr create`, `gh issue create`, `gh release create` | | **Destructive** | `AskUserQuestion` BEFORE executing | `gh pr merge`, `gh pr close`, `gh release delete` | | **Forbidden** | Multi-step validation, NEVER auto-confirm | `gh repo delete`, `gh repo transfer`, visibility changes | See [references/safety-rules.md](references/safety-rules.md) for the full classification and confirmation templates. ## Decision Flow ``` Command received → Classify risk tier (see Quick Reference) → Safe? Execute immediately → Write? Inform user what will happen → execute → Destructive? A