corvus-review-r1

Gather PR context and external context into a structured REVIEW_CONTEXT.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews often lack complete context, causing delays and misinterpretations. This Skill automates gathering and consolidating PR context and external context for fast, accurate reviews.

Core Features & Use Cases

  • Parallel PR context gathering for changed files, diffs, and git history.
  • External context collection (linked issues, CI status, related PRs) to inform decisions.
  • Structured output as a REVIEW_CONTEXT for downstream automation and auditing.

Quick Start

Provide a PR identifier or URL to trigger parallel context gathering and produce a complete REVIEW_CONTEXT.

Frequently Asked Questions about corvus-review-r1

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

FAQPage Schema
How do I gather context for code review on large pull requests?

Code review context gathering automates reading changed files, diffs, and git history to produce a structured REVIEW_CONTEXT output. It launches parallel workstreams to consolidate internal PR data and external context like linked issues for large codebases.

What is parallel PR review context and how does it work?

Parallel PR review context is a structured output created by running dual workstreams simultaneously. It captures changed files, diffs, and git history alongside external context like linked issues and CI status to inform reviewer decisions.

Can I automate collecting linked issues and CI status for PR reviews?

Yes, you can automate collecting linked issues and CI status as part of external context gathering. The process runs in parallel with internal PR data collection to output a complete REVIEW_CONTEXT for downstream validation and auditing.

Does automated PR context gathering work for large codebases?

Yes, automated PR context gathering is designed for large codebases. It parallelizes data gathering to read changed files, diffs, and git history efficiently, ensuring reviewers get consolidated context without delays.

How do I start automated code review context gathering?

Provide a PR identifier or URL to trigger parallel context gathering across changed files, diffs, and git history. This produces a structured REVIEW_CONTEXT output ready for downstream validation and auditing.

What are the limitations of automated dependency graph and PR context gathering?

Automated PR context gathering requires a PR identifier or URL to function. It captures git history and dependency graphs but outputs a structured REVIEW_CONTEXT for downstream validation, rather than performing the actual code review itself.