pr-review

Run parallel GitHub pull request reviews with confidence-scored findings.

4|2|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/saitarrun/devforge-ai --skill pr-review-saitarrun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/saitarrun/devforge-ai/tree/main/skills/pr-review
Command: npx skills add https://github.com/saitarrun/devforge-ai --skill pr-review-saitarrun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual pull request reviews are often inconsistent, miss critical context from git history and prior reviewer feedback, and waste engineering time on low-value nitpicks that don't impact code quality or project compliance.

Core Features & Use Cases

  • 5-Parallel Agent Analysis: Runs simultaneous specialized reviews for CLAUDE.md compliance, obvious bug detection, git history context, prior PR feedback, and code comment adherence.
  • Confidence Scoring Filter: Scores every identified issue 0-100 and only surfaces high-confidence (≥80) findings to eliminate false positive noise for reviewers.
  • SDLC Integration: Fits directly into DevForge AI's testing and pre-deploy quality gates for end-to-end software delivery workflows.

Quick Start

Use the pr-review skill to run a full high-confidence code review on pull request #42 for your current GitHub repository.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I run a high-confidence GitHub PR code review to reduce false positive noise?

Run a high-confidence GitHub PR code review by applying a confidence scoring filter that rates identified issues 0-100, surfacing only findings scoring 80 or above to eliminate low-value nitpicks and false positives for reviewers.

How does multi-agent parallel code review analyze git history and prior PR feedback?

Multi-agent parallel code review uses five specialized agents to simultaneously analyze CLAUDE.md compliance, obvious bugs, git history context, prior PR feedback, and code comment adherence, aggregating their findings for comprehensive historical context analysis.

Do I need GitHub CLI access to automate pull request validation for structured SDLC workflows?

Yes, GitHub CLI access is required to automate pull request validation, as the review process orchestrates parallel agents and extracts historical code context directly from your GitHub-hosted software repositories.

What is the best way to enforce project-specific rule compliance checks before merging a pull request?

The best way to enforce project-specific rule compliance checks is running simultaneous specialized reviews for CLAUDE.md adherence and code comment compliance, filtering out findings below an 80 confidence score to ensure high-impact validation.

Can I integrate automated code review into pre-merge quality gates for end-to-end software delivery?

Yes, you can integrate automated code review directly into pre-merge quality gates and end-to-end software delivery workflows, applying structured SDLC validation and pre-deploy compliance checks before allowing a pull request to merge.