bmad-os-review-pr

Review GitHub pull requests with adversarial and edge-case analysis.

8|2|Updated Feb 1, 2026

Search Tags:#automation #code review #pull request #github #engineering #adversarial

Ready to run

npx skills add https://github.com/bmad-code-org/bmad-utility-skills --skill bmad-os-review-pr-bmad-code-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-os-review-pr
Source: https://github.com/bmad-code-org/bmad-utility-skills/tree/main/skills/bmad-os-review-pr
Command: npx skills add https://github.com/bmad-code-org/bmad-utility-skills --skill bmad-os-review-pr-bmad-code-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the inconsistency and lack of depth in standard code reviews by providing a rigorous, dual-layer analysis that combines adversarial skepticism with mechanical edge-case detection.

Core Features & Use Cases

Adversarial Review: Employs a cynical persona to identify logic gaps, security risks, and code smells that standard reviews often miss.
Edge Case Hunting: Automatically scans code for boundary conditions, null dereferences, and unhandled exceptions.
Professional Synthesis: Merges findings into a neutral, actionable, and high-quality engineering report ready for immediate feedback.

Quick Start

Use the bmad-os-review-pr skill to perform a deep review of pull request number 123 in the current repository.

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 automate an adversarial code review for a GitHub pull request?▼

To automate adversarial code review, this Skill performs a dual-layer analysis combining adversarial skepticism with automated edge-case detection on GitHub pull requests, generating professional, actionable engineering feedback.

Why does my standard pull request review miss logic gaps and security risks?▼

Standard pull request reviews often miss logic gaps and security risks due to a lack of rigorous depth. An adversarial review approach actively hunts for boundary conditions, null dereferences, and unhandled exceptions to resolve this inconsistency.

Do I need the GitHub CLI and local repository access to run automated PR analysis?▼

Yes, performing automated pull request analysis requires the GitHub CLI and local repository access. These dependencies are necessary to execute diff analysis and post the resulting review comments back to the specific pull request.

What is the best way to find edge cases and null dereferences in a pull request?▼

The best way to find edge cases and null dereferences is using a dual-layer review mechanism. It automatically scans code for boundary conditions and unhandled exceptions while an adversarial persona evaluates logic gaps and security risks.

How do I post professional engineering feedback to a specific GitHub PR?▼

To post professional engineering feedback, the review Skill operates on specific pull request identifiers. It merges adversarial findings and edge-case detections into a neutral report, then uses the GitHub CLI to post comments.