pr-reviewer

Audit GitHub pull requests for correctness, conventions, tests, and lint findings.

3|Updated Mar 16, 2026

Search Tags:#automation #review #quality-assurance #lint #pull-request #pr-review #gh-cli

Ready to run

npx skills add https://github.com/hcross/crewrig --skill pr-reviewer-hcross

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-reviewer
Source: https://github.com/hcross/crewrig/tree/main/.gemini/skills/pr-reviewer
Command: npx skills add https://github.com/hcross/crewrig --skill pr-reviewer-hcross

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, shellcheck, markdownlint, ruff, flake8, yq, git, and includes scripts (resource) components.

What problem does it solve?

Independent PR review without authorship context to ensure correctness, adherence to conventions, and test coverage.

Core Features & Use Cases

Independent PR analysis: fetches the PR diff via gh pr diff and analyzes across correctness, conventions, tests, and lint findings.
Structured verdict outputs: emits a verdict of Approve, Request Changes, or Comment with a clear justification.
Guided five-step protocol: follows the defined steps for consistent, auditable reviews.

Quick Start

Invoke the pr-reviewer to audit a pull request by fetching the diff with gh and applying the five-step review protocol.

Frequently Asked Questions about pr-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate a GitHub pull request review without author bias?▼

Automating pull request review without author bias involves analyzing the diff fetched via gh CLI across correctness, conventions, and tests. This Skill applies a structured five-step protocol to emit impartial verdicts like Approve or Request Changes.

How does an automated PR reviewer evaluate code conventions and test coverage?▼

An automated PR reviewer evaluates conventions and test coverage by applying linting scripts using shellcheck, markdownlint, ruff, and flake8. It analyzes the fetched diff against these checks to ensure adherence to project standards and test completeness.

Do I need gh CLI installed to run automated pull request audits?▼

Yes, you need gh CLI installed to run automated pull request audits. The review process relies on gh to fetch the PR diff and post the final review verdict, alongside dependencies like jq, yq, and git for data processing.

What is the best way to post structured verdicts like Approve or Request Changes on GitHub?▼

The best way to post structured verdicts like Approve or Request Changes is to use a guided five-step review protocol that analyzes the diff and linter findings, then submits the final evaluation back to GitHub via the gh CLI tool.

What limitations should I expect when using linters for independent PR analysis?▼

Limitations when using linters for independent PR analysis include dependency on specific tools like ruff and flake8 for Python or shellcheck for shell scripts. The automated review focuses on syntax and convention compliance, which may miss nuanced logic errors not caught by linters.