ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity
BMAD-METHOD/.claude/skills/bmad-os-review-pr
History
Alex Verkhovsky 675e753e9b
refactor(skills): convert review-pr and audit-file-refs to bmad-os skills (#1732) 
Move Raven PR review and file-ref audit from tools/ into
.claude/skills/ as proper bmad-os skills with SKILL.md + prompts/
instructions.md split pattern. Strip XML tags from Raven content,
promote sections to H2 headings. Delete originals from tools/.

Co-authored-by: Brian <bmadcode@gmail.com>
 		2026-02-22 10:46:32 -06:00
..
prompts refactor(skills): convert review-pr and audit-file-refs to bmad-os skills (#1732) 2026-02-22 10:46:32 -06:00
README.md refactor(skills): convert review-pr and audit-file-refs to bmad-os skills (#1732) 2026-02-22 10:46:32 -06:00
SKILL.md refactor(skills): convert review-pr and audit-file-refs to bmad-os skills (#1732) 2026-02-22 10:46:32 -06:00

README.md

Raven's Verdict - Deep PR Review Tool

Adversarial code review for GitHub PRs. Works with any LLM agent.

Status: Experimental. We're still figuring out how to use this effectively. Expect the workflow to evolve.

How It Works

Use /bmad-os-review-pr to review a specific PR:

"Use /bmad-os-review-pr to review PR #123"

The tool will:

  1. Check out the PR branch locally
  2. Run an adversarial review (find at least 5 issues)
  3. Transform findings into professional tone
  4. Preview the review and ask before posting

See prompts/instructions.md for full prompt structure, severity ratings, and sandboxing rules.

When to Use

Good candidates:

  • PRs with meaningful logic changes
  • Refactors touching multiple files
  • New features or architectural changes

Skip it for:

  • Trivial PRs (typo fixes, version bumps, single-line changes)
  • PRs you've already reviewed manually
  • PRs where you haven't agreed on the approach yet — fix the direction before the implementation

Workflow Tips

Always review before posting. The preview step exists for a reason:

  • [y] Yes — Post as-is (only if you're confident)
  • [e] Edit — Modify findings before posting
  • [s] Save only — Write to file, don't post

The save option is useful when you want to:

  • Hand-edit the review before posting
  • Use the findings as input for a second opinion ("Hey Claude, here's what Raven found — what do you think?")
  • Cherry-pick specific findings

Trust but verify. LLM reviews can miss context or flag non-issues. Skim the findings before they hit the PR.

Prerequisites

  • gh CLI installed and authenticated (gh auth status)
  • Any LLM agent capable of running bash commands