dev-review-pr

Aggregate CodeRabbit and Claude PR feedback and validate GitHub Actions checks.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/code-review-benchmark/coderabbit_prs2__forge-gpu__coderabbit__PR323__20260317 --skill dev-review-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-review-pr
Source: https://github.com/code-review-benchmark/coderabbit_prs2__forge-gpu__coderabbit__PR323__20260317/tree/main/.claude/skills/dev-review-pr
Command: npx skills add https://github.com/code-review-benchmark/coderabbit_prs2__forge-gpu__coderabbit__PR323__20260317 --skill dev-review-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates PR review workflows by aggregating automated feedback (CodeRabbit, Claude), validating GitHub Actions status, and guiding when a PR is ready to merge.

Core Features & Use Cases

  • Aggregate CodeRabbit and Claude review feedback from PRs, including inline threads and review bodies.
  • Track GitHub Actions status and report pending or failed checks, minimizing wasted review rounds.
  • Identify the latest review round and surface both inline comments and duplicate or nitpick items across rounds.
  • Coordinate pre-merge steps: update branch if behind main, resolve conversations, and ensure checks pass before merging.

Quick Start

Run /dev-local-review to validate changes, then run /dev-review-pr <pr-number> to fetch the latest feedback and guide the merge.

Frequently Asked Questions about dev-review-pr

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

FAQPage Schema
How do I aggregate CodeRabbit and Claude PR review feedback before merging?

Aggregating automated PR review feedback involves fetching inline comments and review bodies from CodeRabbit and Claude. It identifies the latest review round, surfaces duplicate nitpick items, and checks GitHub Actions status before guiding merge readiness.

What is the best way to automate GitHub PR merge readiness checks?

Automating GitHub PR merge readiness checks involves orchestrating GitHub Actions status validation and aggregating automated bot feedback. It ensures branches are updated behind main, conversations resolved, and all checks pass before merging.

How do I handle duplicate inline comments across multiple PR review rounds?

Handling duplicate inline comments across multiple PR review rounds involves identifying the latest review iteration and surfacing recurring nitpick feedback. This ensures only unresolved issues are tracked before proceeding to merge.

Can I use this workflow to update a GitHub branch that is behind main before merging?

Yes, this workflow coordinates pre-merge steps including updating your branch if it falls behind main. It ensures proper conversation resolution and validates that all GitHub Actions checks pass before the final merge.

Does this PR review automation work with GitHub Actions status validation?

Yes, this PR review automation tracks GitHub Actions status to report pending or failed checks. It minimizes wasted review rounds by ensuring all validation checks pass before guiding the merge process.

Why does my automated PR review workflow keep failing before merge?

Automated PR review workflows often fail due to pending GitHub Actions checks or unresolved inline comments. This workflow validates check status, aggregates bot feedback, and ensures branch updates and conversation resolution before merging.