pr-review

Analyze pull request changes, risks, and compliance with project standards.

Updated Apr 24, 2026

Search Tags:#code-quality #risk-assessment #pull-request #pr-review #security-review #diff-analysis

Ready to run

npx skills add https://github.com/bc05/codex-skills --skill pr-review-bc05

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill facilitates a thorough technical review of pull requests, identifying changes, risks, security concerns, and gaps in tests, to guide safer merges.

Core Features & Use Cases

Analyze all changes in a PR, not just a summary, and assess risks, quality, and test coverage.
Prioritize issues by severity and provide descriptive, actionable feedback within the diff context.
Support PRs identified by number or URL and generate a consolidated review ready for maintainers.

Quick Start

Diga ao assistente para revisar o PR identificado por número ou link e retornar um relatório com riscos, mudanças e sugestões.

Frequently Asked Questions about pr-review

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

FAQPage Schema

How do I review a pull request for security risks and code quality?▼

A pull request review analyzes all changes in a PR to assess risks, quality, and test coverage. It identifies security concerns and compliance gaps, generating a consolidated review with prioritized, actionable feedback to guide safer merges.

Can I analyze a pull request using just the PR number or URL?▼

Yes, you can analyze a pull request using its PR number or URL. The skill extracts the changes from that identifier, limits assessment to the provided PR details and repository context, and outputs a consolidated review ready for maintainers.

How do I generate actionable risk notes for a code diff before merging?▼

To generate actionable risk notes for a code diff, evaluate all changes against project standards and security protocols. Prioritize identified vulnerabilities by severity and provide descriptive feedback directly within the diff context to guide project governance.

What is the best way to automate developer audits for pull requests?▼

The best way to automate developer audits for pull requests is to systematically analyze the entire diff, not just a summary, and output a consolidated review. This approach identifies compliance gaps and test coverage issues, producing a concise summary for project governance.

Does a thorough PR review check for test coverage gaps and project standards compliance?▼

Yes, a thorough PR review checks for test coverage gaps and project standards compliance. By analyzing all changes in the pull request, it identifies missing tests and deviations from project standards, prioritizing these issues by severity to provide actionable feedback for maintainers.