bmad-code-review

Review code changes using adversarial layers to identify issues and suggest improvements.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/peshay/portfolixir --skill bmad-code-review-peshay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-code-review
Source: https://github.com/peshay/portfolixir/tree/main/.claude/skills/bmad-code-review
Command: npx skills add https://github.com/peshay/portfolixir --skill bmad-code-review-peshay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the code review process by using adversarial review layers to identify issues and suggest improvements, ensuring code quality and compliance.

Core Features & Use Cases

  • Adversarial Reviews: Utilizes parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) for comprehensive code analysis.
  • Structured Triage: Organizes findings into actionable categories for efficient issue resolution.
  • Use Case: When a developer wants to review code changes, this Skill can be activated to automatically perform a thorough review and provide actionable feedback.

Quick Start

Run the bmad-code-review skill to start a code review session.

Frequently Asked Questions about bmad-code-review

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

FAQPage Schema
What is an adversarial code review and how does it identify compliance issues?

Adversarial code review uses parallel layers like Blind Hunter and Edge Case Hunter to proactively find hidden issues and compliance violations in code changes. It actively hunts for flaws rather than passively reading, generating structured actionable suggestions for software development workflows.

How do I run an adversarial code review on my recent code changes?

Run the review skill to start a session that automatically executes multiple adversarial review steps across parallel layers on your code changes. It then organizes all findings into structured, actionable categories for efficient issue triage and resolution.

Can I use this adversarial review approach for tracking code quality issues in software development?

Yes, this approach is designed for software development workflows requiring code quality and compliance checks. It tracks code quality issues by organizing adversarial findings into structured triage categories for efficient resolution.

What is the difference between adversarial code review layers and standard static code analysis?

Adversarial review layers actively probe code changes from different perspectives like edge cases and acceptance criteria, while standard analysis applies fixed rule sets. This multi-layer approach provides comprehensive analysis and structured triage of findings.

What are the limitations of using automated adversarial layers for code compliance checks?

A limitation is that handling findings from different adversarial layers requires executing multiple review steps and manual oversight to resolve triaged issues. It focuses on identifying issues and suggesting improvements rather than automatically fixing the code.