← ClaudeAtlas

review-prlisted

When the user wants to review someone's GitHub pull request, approve it, or leave feedback on it. Also use when the user mentions "review this PR", "code review", "look at this pull request", "what do you think of this PR", "approve this PR", "request changes", or pastes a GitHub pull request URL asking for an opinion.
Sahil2004/skills · ★ 0 · Code & Development · score 59
Install: claude install-skill Sahil2004/skills
# Review PR Review a GitHub pull request, then either approve it cleanly or post structured, severity-classified feedback. A correct PR is approved with no comments attached; a PR with findings gets those findings and no approval. ## When to use - "Review PR 412" / a pasted `https://github.com/<org>/<repo>/pull/<n>` URL. - "Is this PR safe to merge?" (answering "yes, nothing blocking" is a valid outcome) - "Look over these changes and tell me what's wrong." - "Approve this PR if it's fine." Do not use this when the user wants to **answer** review comments already left on their own PR; this skill produces feedback, it does not reply to it. Also skip this when the change is not on GitHub yet (review the working tree directly) or the user only wants a PR description. ## Prerequisites ```bash gh auth status # must be logged in ``` If `gh` is missing or unauthenticated, stop and tell the user; do not guess at PR content. **Command economy is a hard requirement.** Every script here batches into a single API call. Never poll, never loop a command per file, and never dump raw JSON into context. See `references/gh-commands.md` for the anti-patterns to avoid. ## Workflow 1. **Load the PR in one call.** Metadata, file churn, CI status, existing reviews, and open threads all come back from a single request: ```bash bash scripts/pr_context.sh <owner/repo> <n> ``` Then fetch the diff once and reuse it: ```bash gh pr diff <n> --repo <owner/repo>