pr-review

Analyze code diffs and pull requests to produce severity-ranked findings with file:line locations.

310|45|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Mathews-Tom/praxis-skills --skill pr-review-mathews-tom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/Mathews-Tom/praxis-skills/tree/main/skills/pr-review
Command: npx skills add https://github.com/Mathews-Tom/praxis-skills --skill pr-review-mathews-tom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides focused, high-precision code reviews for pull requests and diffs so teams find and prioritize the most important defects before merge, reducing regressions and review noise.

Core Features & Use Cases

  • Diff routing across five dimensions: selectively load methodologies for code quality, test coverage, error handling, type design, and comment quality based on changed files.
  • Severity-ranked findings with confidence: report Critical, Important, and Suggestion issues with confidence scores and mandatory file:line locations.
  • Deduplication and calibration rules: merge overlapping findings, respect project CLAUDE.md rules, and favor precision over noisy recommendations.
  • Use Case: run on a feature branch or PR to produce an actionable pre-merge report that highlights security regressions, silent failures, test gaps, and type/design regressions.

Quick Start

Review my current git diff and produce a severity-ranked PR review with file:line references and suggested fixes.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I perform a diff-based code review on a pull request?

Perform a diff-based code review by analyzing changed files to identify high-confidence issues, routing checks across code quality, test coverage, error handling, type design, and comment quality. Produce severity-ranked findings with file:line locations and recommended actions.

What is the best way to prioritize critical fixes in a PR review?

Prioritize critical fixes in PR reviews by reporting Critical, Important, and Suggestion issues with confidence scores. Deduplicate overlapping findings and favor precision over noisy recommendations to reduce regressions and review noise.

How does diff routing work for test coverage and error handling checks?

Diff routing selectively loads methodologies for test coverage and error handling based on the specific changed files in the pull request. This targeted approach ensures only relevant code quality dimensions are evaluated.

Can I use CLAUDE.md rules to calibrate code review findings?

Use CLAUDE.md rules to calibrate code review findings by respecting project-specific configurations. Deduplication and calibration rules merge overlapping findings and favor precision over noisy recommendations for your pre-merge report.

How do I identify silent failures and type design regressions before merge?

Identify silent failures and type design regressions by running diff-based code reviews on a feature branch. Generate an actionable pre-merge report highlighting security regressions, test gaps, and type issues with mandatory file:line locations.

What are the limitations of automated diff analysis for pre-merge reviews?

Automated diff analysis focuses only on changed files to produce high-precision code reviews. It targets high-confidence issues and deduplicates findings, but does not evaluate the entire repository context outside the current diff.