What problem does it solve? Working with the GitHub CLI involves dozens of command groups, version-dependent flags, and subtle pitfalls like silent GET-to-POST method switches or identity drift between accounts. This Skill gives an agent a structured reference for routing gh commands correctly, classifying them by safety level, and avoiding destructive mistakes. ## Core Features & Use Cases - Command routing reference: Complete tables of gh command groups (issue, pr, repo, run, release, api, auth, extension, and more) with their subcommands and purposes. - Three-tier safety model: Classifies commands as read-only, mutating, or destructive, with rules such as never pre-filling --yes on destructive operations. - gh api guidance: Covers REST and GraphQL calls, pagination with --paginate and --slurp, typed vs raw fields (-F vs -f), and common pitfalls like placeholder resolution from git remotes. - Authentication and identity drift handling: Explains token methods, OAuth scopes, multi-account switching, and the authoritative gh api /user check to verify the active account before mutations. - Use Case: When asked to merge a pull request or delete a release, the agent consults the safety model, runs gh <command> --help for current flags, verifies the active GitHub identity, and only then executes the mutating command. ## Quick Start Ask the agent to list open pull requests with their authors and check CI run status for the current repository using the gh CLI.