Our review

This skill leverages the `gh` command-line tool to interact with GitHub for managing pull requests, issues, and releases.

When to use it

When you need to quickly view or modify GitHub items (PRs, issues, releases) without leaving your command-line environment.

When not to use it

For operations requiring a rich graphical interface or complex GitHub API interactions (prefer direct API use then).

name: gh-cli description: Interact with GitHub repositories, PRs, and issues using the `gh` CLI. Use when the user asks to "list PRs", "check out PR", "view issue", or "create release". allowed-tools: Bash

Use GitHub CLI

Ensure gh is available and authenticated: run gh auth status (do not use --show-token); respect GH_HOST if set. Prefer GH_TOKEN/GITHUB_TOKEN env auth; never print tokens or add them to files.
Set repo context explicitly with --repo owner/name or by checking the current repo via gh repo view; avoid assuming defaults.
Prefer structured output with --json fields and --limit to keep responses concise (e.g., gh pr list --state open --json number,title,author,headRefName,baseRefName,url --limit 20).
Common reads: gh pr view <number> --json number,title,state,author,mergedAt,commits,files,comments,url, gh issue list --state all --json number,title,state,author,url --limit 30, gh release list --limit 20, gh release view <tag> --json tagName,name,publishedAt,url.
For write operations (create/update PRs, issues, comments, releases), confirm intent and required fields; use --title, --body, or --body-file without secrets. Avoid noisy outputs; capture URLs/results only.
When checking out PRs locally, use gh pr checkout <number> and handle branch existence gracefully; do not alter remotes or push unless explicitly requested.