corvus-review-r3

Synthesize PR review findings into a GitHub-compatible REVIEW_DOCUMENT with deduplication and filtering.

3|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/NachoFLizaur/corvus --skill corvus-review-r3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: corvus-review-r3
Source: https://github.com/NachoFLizaur/corvus/tree/main/skill/corvus-review-r3
Command: npx skills add https://github.com/NachoFLizaur/corvus --skill corvus-review-r3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform raw REVIEW_FINDINGS into a polished, deduplicated, actionable REVIEW_DOCUMENT suitable for GitHub reviews.

Core Features & Use Cases

  • Deduplication: Merges duplicate findings across passes, keeps the highest-severity context, and logs merges for traceability.
  • Filtering & Suppression: Applies false-positive filtering, severity thresholds, and suppression rules to keep review signal crisp and relevant.
  • Review Rendering: Produces a GitHub-compatible REVIEW_DOCUMENT with a structured summary, inline comments, and a final action decision.
  • Use Case: Used in Phase R3 to convert cross-pass findings into a complete, ready-to-submit code review.

Quick Start

Generate a complete R3 review by synthesizing findings from the PR context and generating a REVIEW_DOCUMENT.

Frequently Asked Questions about corvus-review-r3

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

FAQPage Schema
How do I convert raw code review findings into a GitHub-compatible review document?

You can synthesize raw findings into a GitHub-compatible review document by applying deduplication, false-positive filtering, and severity suppression to generate a structured summary with inline comments.

What is PR review deduplication and how does it handle overlapping findings?

PR review deduplication merges duplicate findings across multiple analysis passes, retains the highest-severity context, and logs the merges to ensure traceability in the final review output.

Can I automatically approve or request changes based on PR review severity?

Yes, you can automatically generate an action decision to APPROVE, REQUEST_CHANGES, or COMMENT_ONLY based on filtered findings, severity thresholds, and nit-budget enforcement rules.

How do I filter false positives and suppress low-severity issues in automated PR reviews?

You can filter false positives and suppress low-severity issues by applying severity thresholds and suppression rules consistent with your PR configuration context to keep the review signal crisp.

What is the best way to enforce a nit-budget limit during code review rendering?

The best way to enforce a nit-budget is by synthesizing cross-pass findings into a structured document that automatically filters excessive nitpick comments based on your configured review limits.

Why are my GitHub inline comments duplicated across multiple review passes?

Duplicate inline comments occur when raw findings overlap across passes; applying a deduplication phase merges these findings, keeps the highest severity, and renders a single clean review document.