pr-review

Name: pr-review
Availability: InStock
Author: offlinecv

Review pull requests against issue acceptance criteria and architectural gates.

8|Updated May 29, 2026

Search Tags:#automation #quality assurance #code review #pull request #security #github

Ready to run

npx skills add https://github.com/offlinecv/OfflineCV --skill pr-review-offlinecv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/offlinecv/OfflineCV/tree/main/.claude/skills/pr-review
Command: npx skills add https://github.com/offlinecv/OfflineCV --skill pr-review-offlinecv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, npm, npx.

What problem does it solve?

This skill solves the problem of superficial pull request reviews by enforcing a rigorous, adversarial audit process that prioritizes the issue spec over the PR's own claims.

Core Features & Use Cases

Adversarial Audit: Validates code against linked issue acceptance criteria while treating the PR description as a hypothesis to be tested.
OfflineCV Gatekeeping: Automatically enforces house rules including fixture PII checks, design-system reuse, style token compliance, and dead-code analysis.
Command-Level Security: Reviews bash and GitHub CLI scripts for common bugs like word-splitting, injection, and non-idempotent writes.

Quick Start

Invoke the pr-review skill by providing the pull request number to initiate an automated, multi-gate adversarial review of the changes.

Frequently Asked Questions about pr-review

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

FAQPage Schema

How do I automate an adversarial code review for a GitHub pull request?▼

An adversarial code review audits a pull request by validating diffs against linked issue acceptance criteria and architectural gates. It treats the PR description as a hypothesis, executing automated checks for security, dead code, and fixture PII.

What is an adversarial PR audit and how does it differ from standard code review?▼

An adversarial PR audit prioritizes the linked issue spec over the PR description's claims. It enforces maintainer-grade quality by automatically checking for design-system compliance, command-level script vulnerabilities, and non-idempotent writes.

Can I check bash and GitHub CLI scripts for injection vulnerabilities during a PR review?▼

Yes, command-level security audits review bash and GitHub CLI scripts for common bugs like word-splitting, injection, and non-idempotent writes. This ensures shell automation within the pull request meets maintainer-grade quality standards.

How do I validate pull request diffs against issue acceptance criteria?▼

Validating pull request diffs against issue acceptance criteria involves analyzing the code for correctness and architectural gate compliance. The process audits the PR description for accuracy while executing checks for dead code and fixture PII.

Do I need to install npm and gh CLI to run automated pull request security checks?▼

Yes, automated pull request security checks require the gh, git, npm, and npx dependencies. These tools facilitate the command-level script analysis, repository diff validation, and architectural gate enforcement required for an adversarial audit.

What is the best way to enforce design-system reuse and style token compliance in a pull request?▼

Enforcing design-system reuse and style token compliance is achieved through automated house rule gatekeeping during an adversarial PR review. This process audits the diff against project-specific architectural gates to ensure maintainer-grade standards.