| name | github |
| description | Inspect GitHub PRs, issues, CI, and publish flows with local git and gh. |
| when_to_use | Use when the task depends on GitHub repository, pull request, issue, check, review, or publish state. |
| triggers | ["github","pull request","pr","issue","gh pr","gh issue"] |
GitHub
Use this skill to orient GitHub work before choosing a narrower workflow.
Start by identifying the repository and target object:
- Inspect
git remote -v, the current branch, and git status --short.
- Verify
gh auth status when a GitHub command is needed.
- For pull requests, prefer
gh pr view <number-or-url> --json number,title,state,baseRefName,headRefName,headRefOid,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup,url.
- For issues, prefer
gh issue view <number-or-url> --json number,title,state,author,labels,body,comments,url.
Route to the focused skill when the user asks for a specific workflow:
- Use
ci-debug for failing GitHub Actions checks.
- Use
publish-changes when committing, pushing, or opening a PR.
- Use
review-follow-up when addressing unresolved PR review feedback.
When comparing GitHub state to local code, keep the exact head SHA visible in the reasoning. If the local checkout is dirty, stale, or on a different branch than the PR head, inspect safely before editing and avoid overwriting unrelated user changes.
/review is the code-review workflow. This skill is broader GitHub orientation: metadata, issues, CI state, review threads, branches, and publish flow triage.