pr-reviewer

Review pull requests with CI status, conventions, diff evidence, and linter output.

20|4|Updated May 14, 2026
One-click install
npx skills add https://github.com/crewrig/crewrig --skill pr-reviewer-crewrig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-reviewer
Source: https://github.com/crewrig/crewrig/tree/main/artifacts/core/skills/pr-reviewer
Command: npx skills add https://github.com/crewrig/crewrig --skill pr-reviewer-crewrig

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you audit pull requests as an independent reviewer, so you can catch real defects, convention violations, and test gaps before merge without relying on author context.

Core Features & Use Cases

  • CI-aware preflight: Checks required CI status first and blocks approval when a required check is failing or still pending.
  • Convention and diff review: Reads repository rules, inspects the PR diff, and evaluates correctness against project conventions and linked issues.
  • Linter-backed findings: Runs the bundled shell, markdown, Python, JSON, and skill validators when relevant and reports results in a structured review.
  • Use case: A maintainer asks for a cold review of a feature PR and needs a verdict that cites file paths, line ranges, and any linter output.

Quick Start

Use the pr-reviewer skill to assess pull request 42 in this repository and return a structured verdict with CI status, findings, and a clear approve, request changes, or comment outcome.

Frequently Asked Questions about pr-reviewer

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

FAQPage Schema
How do I review a pull request against project conventions and CI status?

Review a pull request against project conventions and CI status by inspecting the diff, checking required CI checks, and running linters to produce a structured approve, request changes, or comment verdict.

Can I block a PR merge when a required CI check is failing?

Yes, CI-aware preflight checks required CI status first and blocks approval when a required check is failing or still pending, ensuring merge readiness before proceeding with diff review.

How do I automate code review using linter output and diff evidence?

Automate code review using linter output and diff evidence by running bundled shell, markdown, Python, JSON, and skill validators, then grounding structured findings in file paths and line ranges.

Do I need GitHub CLI access to perform an automated pull request review?

Yes, GitHub CLI access is required to fetch PR diffs, evaluate CI status, and assess merge readiness as an independent reviewer without relying on author context.

What is the best way to audit documentation updates and script modifications before merge?

Audit documentation updates and script modifications before merge by applying cold-review validation that checks repository rules, runs relevant linters, and surfaces actionable findings with a clear verdict.

Does the code review process work with shell, markdown, and Python validators?

Yes, the code review process works with shell, markdown, and Python validators, running bundled shellcheck, markdownlint, ruff, flake8, jq, and yq linters when relevant to verify claims and report results.