skills.rest
NachoFLizaur
NachoFLizaurCOMMUNITY
Explore all skills by this author →
GitHub

corvus-review-r0

Parse PR references, fetch metadata via gh pr view, and produce PR_CONTEXT.

3|Updated Dec 18, 2025
Search Tags:#automation#github#config#metadata#review#pr#triage
One-click install
npx skills add https://github.com/NachoFLizaur/corvus --skill corvus-review-r0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: corvus-review-r0
Source: https://github.com/NachoFLizaur/corvus/tree/main/skill/corvus-review-r0
Command: npx skills add https://github.com/NachoFLizaur/corvus --skill corvus-review-r0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the initial PR intake, triage, and metadata loading to standardize downstream review.

Core Features & Use Cases

  • Parse PR references (URL, #number, owner/repo#number) and fetch core metadata.
  • Load per-project review configuration and merge with defaults.
  • Produce a structured PR_CONTEXT used by downstream R1 reviewers.

Quick Start

Provide a PR reference (URL, #number, or owner/repo#number) to initialize the R0 workflow.

Frequently Asked Questions about corvus-review-r0

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

FAQPage Schema
How do I automate PR triage and metadata loading for GitHub reviews?▼

Automating PR triage involves parsing PR references, fetching core metadata via gh pr view, loading review config, and producing a structured PR_CONTEXT for downstream reviewers. This Skill standardizes that initial intake process automatically.

What GitHub PR reference formats can I use to initialize automated triage?▼

You can provide a PR reference as a URL, an issue number like #number, or the owner/repo#number format to initialize the triage workflow and fetch core metadata.

Can I use this PR triage automation across internal repos and forks?▼

Yes, this automation applies to PR-based review workflows across both internal repos and forks, enabling consistent metadata gathering and triage regardless of repository origin.

How does automated PR intake load per-project review configuration?▼

Automated PR intake loads per-project review configuration and merges it with defaults, producing a structured PR_CONTEXT that downstream R1 review processes can consume consistently.

What is the best way to standardize GitHub PR metadata for downstream review?▼

Standardizing GitHub PR metadata requires parsing references, fetching core metadata via gh pr view, and producing a structured PR_CONTEXT, which this Skill automates to ensure consistent downstream review.

Related Skills

Explore More Software Engineering Skills→
funsaizedfunsaized
1

review-pr

Review GitHub pull requests for bugs, regressions, missing tests, and risky changes.

Community
Intermediate
wangzhongyuan11wangzhongyuan11
1

demo-review-2

Automate Python code review with pylint, bandit, and pytest.

Community
Intermediate
sakurosakuro
2

merge-pr

Merge GitHub pull requests with the gh CLI after validating CI checks and approvals.

Community
Intermediate
joelhooksjoelhooks
729

pr-triage

Fetch PR comment metadata first and expand bodies on demand.

Community
Advanced