pr-review

Analyze pull requests for correctness, quality, and safety issues.

1|1|Updated Jun 11, 2024
One-click install
npx skills add https://github.com/ag-grid/ag-shared --skill pr-review-ag-grid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/ag-grid/ag-shared/tree/main/prompts/skills/pr-review
Command: npx skills add https://github.com/ag-grid/ag-shared --skill pr-review-ag-grid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the review process for pull requests by identifying issues that could impact correctness, quality, or safety, enabling faster and more reliable code reviews.

Core Features & Use Cases

  • Surface critical and actionable findings from PR diffs in a consistent Markdown or JSON format for CI and human review.
  • Enforce a structured review methodology by referencing the co-located _review-core.md to guide the analysis and verdict.
  • Provide a clear summary, categorized findings, and a recommended-action verdict to accelerate merge decisions.

Quick Start

Provide a reviewer-ready report for the current pull request.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate pull request reviews for logic errors and security concerns?

Automated pull request reviews detect logic errors, missing tests, and security concerns by analyzing code diffs. This process outputs a structured verdict with categorized findings and required actions to accelerate merge decisions.

Can I output static analysis findings from PR reviews in JSON format for CI integration?

Static analysis findings from PR reviews can be output in JSON format for CI integration. The review process generates structured data containing a summary, categorized findings, and a recommended-action verdict suitable for automated pipelines.

What is the best way to enforce a consistent code quality review methodology across pull requests?

Enforcing a consistent code quality review methodology requires referencing a standardized analysis guide to evaluate pull requests. This ensures reviews reliably identify correctness, quality, and safety issues while producing a uniform verdict.

How do I check a pull request diff for readability problems before merging?

Checking a pull request diff for readability problems involves analyzing the code changes against a structured review methodology. This surfaces actionable feedback regarding potential readability issues and missing tests in the submitted code.

Does this pull request review process work without external dependencies?

The pull request review process operates without external dependencies. It relies on a co-located methodology file to guide the analysis of code changes, identifying correctness and safety issues independently.

When should I not use automated static analysis for pull request reviews?

Automated static analysis for pull request reviews should not replace manual review when evaluating complex architectural changes. It is designed to surface actionable correctness and quality findings, but final merge decisions require human context.