← ClaudeAtlas

ghlisted

Expert guidance for using the GitHub CLI (gh) to work with repositories, issues, pull requests, Actions, releases, and the GitHub API from the command line. Use this skill whenever the user needs to perform a GitHub workflow or asks to use gh.
mohammadhprp/teammate · ★ 1 · AI & Automation · score 77
Install: claude install-skill mohammadhprp/teammate
# GitHub CLI (`gh`) Skill Use the official `gh` CLI for GitHub operations instead of manually constructing API requests or browser workflows when a supported command exists. ## When to Use This Skill Invoke when the user needs to: - Inspect, create, edit, review, merge, or close pull requests - Search, create, edit, comment on, or close issues - Inspect repositories, branches, releases, tags, or notifications - View, rerun, cancel, or inspect logs for GitHub Actions workflows - Create and manage releases - Query or mutate GitHub resources through the API ## Prerequisites and Authentication Verify that the CLI is installed before executing commands: ```bash gh --version ``` Check the active account and token scopes: ```bash gh auth status ``` If authentication is missing, use the interactive login flow: ```bash gh auth login ``` For automation, prefer a short-lived `GH_TOKEN` or `GITHUB_TOKEN` environment variable. Never print, commit, or include token values in command output, issue bodies, pull requests, or logs. ## Repository Context Most commands infer the repository from the current Git remote. Confirm context when it matters: ```bash git remote -v gh repo view --json nameWithOwner,defaultBranchRef ``` Use `--repo OWNER/REPO` when running outside a checkout or targeting another repository. ## Core Workflows ### Pull Requests ```bash # List and inspect PRs gh pr list --state open gh pr view 123 --comments # Create a PR after pushing the branch git push