review

Analyze code changes to identify bugs and quality issues.

14|2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/brsbl/ottonomous --skill review-brsbl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/brsbl/ottonomous/tree/main/skills/review
Command: npx skills add https://github.com/brsbl/ottonomous --skill review-brsbl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bugs and quality issues in code changes can slip through reviews, leading to defects in production. This skill orchestrates a thorough, prioritized review process using parallel subagents to surface P0-P2 findings and produce a concrete fix plan.

Core Features & Use Cases

  • Parallel subagents analyze diffs to surface findings quickly and comprehensively.
  • Findings are categorized by priority (P0-P2) and synthesized into a single fix plan.
  • Ideal for pre-merge reviews on feature branches, bug fixes, and refactors across teams.

Quick Start

Run /review on a feature branch to start the parallel review and plan fixes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for pull requests to catch bugs before merging?

Automated code review for pull requests analyzes branch diffs to identify bugs and quality issues before merging. It uses parallel subagents to surface findings quickly and categorizes them by priority from P0 to P2 to ensure production stability.

What is the best way to prioritize bug fixes found during a branch diff review?

Prioritizing bug fixes during a branch diff review involves categorizing findings into P0, P1, and P2 severity levels. This process synthesizes the identified code quality issues into a single, actionable fix plan for developers to resolve.

How does parallel subagent analysis work for pre-merge code reviews?

Parallel subagent analysis works by orchestrating multiple subagents to simultaneously examine code changes and diffs. This comprehensive mechanism surfaces bugs and quality issues quickly, generating a synthesized fix plan for pre-merge reviews on feature branches.

Can I use automated quality assurance for refactoring branches and bug fixes?

Yes, automated quality assurance supports pre-merge reviews for refactoring branches and bug fixes across software engineering teams. It analyzes code changes to identify quality issues and produces a concrete fix plan to prevent defects in production.

What are the limitations of automated code review for complex software engineering projects?

Automated code review focuses on analyzing branch diffs to identify bugs and categorize findings by priority. While it generates a concrete fix plan, developers must still manually implement the synthesized fixes to ensure complex project logic remains intact.