rocha-reviewer

Coordinate automated multi-domain code reviews and generate a consolidated Markdown report.

1|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/renato0307/rocha --skill rocha-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rocha-reviewer
Source: https://github.com/renato0307/rocha/tree/main/.claude/skills/rocha-reviewer
Command: npx skills add https://github.com/renato0307/rocha --skill rocha-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates automated, domain-specific code reviews by orchestrating specialized subagents and producing a unified Markdown Code Review Report to help teams identify issues quickly.

Core Features & Use Cases

  • Orchestrates multiple subagents to cover Go idioms, architecture, conventions, Bubble Tea patterns, and documentation.
  • Executes subagents in parallel and aggregates findings into a single Code Review Report.
  • Useful for pull requests or local changes, providing a consolidated view of code quality and maintainability.

Quick Start

Launch a code review in your repository by invoking rocha-reviewer. Rocha will detect changed files, run all four subagents in parallel, and return a Markdown Code Review Report.

Frequently Asked Questions about rocha-reviewer

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

FAQPage Schema
How do I automate a multi-domain code review for a pull request?

To automate a code review, you can orchestrate specialized subagents to assess Go idioms, architecture, conventions, and documentation in parallel, generating a consolidated Markdown report of actionable findings.

What is the best way to review Go code and Bubble Tea patterns together?

Reviewing Go code and Bubble Tea patterns involves orchestrating specialized subagents in parallel to evaluate idioms and framework conventions, aggregating the results into a unified Markdown report.

Can I generate a Markdown code review report from local branch changes?

Yes, you can generate a Markdown code review report from local branch changes by identifying changed files, gathering context, and running specialized subagents in parallel to produce aggregated findings.

Does automated architecture review work without external dependencies?

Automated architecture review operates without external dependencies by orchestrating internal subagents to analyze conventions and architecture, outputting a structured Markdown report.

What are the limitations of orchestrating subagents for code reviews?

The subagent orchestration focuses specifically on Go idioms, architecture, conventions, Bubble Tea patterns, and documentation, limiting its applicability to other programming languages and frameworks.

When do I need a consolidated Markdown report for a code review?

You need a consolidated Markdown report when coordinating multi-domain code reviews across pull requests, requiring a unified view of architecture, documentation, and convention findings from parallel subagents.