bmad-os-review-pr

Name: bmad-os-review-pr
Availability: InStock
Author: GenEd

Identify bugs, edge cases, and maintainability risks in GitHub pull request diffs.

Updated Mar 30, 2026

Search Tags:#code review #pull request #github #edge cases #engineering #regression #bug detection

Ready to run

npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-os-review-pr-geneducation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-os-review-pr
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-os-review-pr
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-os-review-pr-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a rigorous pull request review process that surfaces bugs, edge cases, regressions, and maintainability risks before changes are merged.

Core Features & Use Cases

Dual-layer analysis: Combines an adversarial code review with an edge-case hunter to find issues from different angles.
Structured findings: Produces severity-ranked, deduplicated observations with clear file references and actionable fixes.
Use case: Use it when a developer opens a GitHub pull request and needs a professional review that catches correctness problems, safety gaps, and overlooked boundary conditions.

Quick Start

Ask me to review pull request 123 and I will analyze the diff, merge the findings, and present a professional review summary.

Frequently Asked Questions about bmad-os-review-pr

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

FAQPage Schema

How do I review a GitHub pull request for edge cases and regressions?▼

Review a GitHub pull request for edge cases by analyzing the diff with a dual-layer process: adversarial code review combined with boundary condition hunting. This catches regressions and safety gaps before merging changes.

Can I use automated code review to find bugs in large pull request change sets?▼

Automated code review supports large pull request change sets through size gating and deduplicated findings. It applies adversarial scrutiny to extensive diffs, identifying maintainability risks and correctness problems across the codebase.

What is the best way to catch maintainability risks in a PR before merging?▼

The best way to catch maintainability risks in a PR is structured analysis that produces severity-ranked observations with clear file references. This dual-layer approach merges adversarial review with edge-case detection for actionable fixes.

Does pull request review work with cross-repo diffs and explicit PR numbers?▼

Pull request review works with cross-repo diffs and requires an explicit PR number or URL. The process verifies a clean checkout before analyzing the provided GitHub pull request diff for bugs and boundary conditions.

How do I get severity-ranked observations from a GitHub PR code review?▼

Get severity-ranked observations from a GitHub PR code review by running dual-layer analysis that merges and deduplicates findings. The output includes clear source tags and file references for identified bugs and maintainability risks.

When should I not use automated adversarial code review for a pull request?▼

Adversarial code review for a pull request should not be used without an explicit PR number or URL, or when a clean checkout cannot be verified. Size gating also limits analysis of excessively large diffs beyond supported thresholds.