zoo-uberreview

Review files under .zoo/review/ and synthesize findings into a prioritized report.

5|1|Updated Aug 22, 2025
One-click install
npx skills add https://github.com/andreyvit/zoo --skill zoo-uberreview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zoo-uberreview
Source: https://github.com/andreyvit/zoo/tree/main/.codex/skills/zoo-uberreview
Command: npx skills add https://github.com/andreyvit/zoo --skill zoo-uberreview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Launches exhaustive per-file Uberreview reviews across all files under .zoo/review/ to ensure nothing is missed and every issue is surfaced.

Core Features & Use Cases

  • Per-file reviewer orchestration: launches dedicated reviewer agents for each file under .zoo/review/ and aggregates findings into a single report.
  • Prioritized triage: categorizes findings into P1, P2, P3 with clear remediation guidance.
  • Cross-reference guidance: automatically consults policy files like .zoo/coding.md, .zoo/testing.md, .zoo/codereview.md, and planning docs when present.
  • Use Case: A repo with 5 review files gets a consolidated report highlighting critical blockers and suggested fixes.

Quick Start

Run the uberreview on the repository to produce a single consolidated report from all files under .zoo/review/.

Frequently Asked Questions about zoo-uberreview

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

FAQPage Schema
How do I automate code review across an entire repository?

Automate repository code review by orchestrating dedicated subagents to analyze every file individually, extracting and categorizing findings into a single consolidated review report.

How does subagent-based code review prioritize issues?

Subagent-based code review prioritizes issues by categorizing findings into a hierarchical P1, P2, and P3 triage scheme, ensuring critical blockers are highlighted with clear remediation guidance.

Can I cross-reference custom coding and testing policies during an automated review?

Automated review can cross-reference custom guidance by automatically consulting policy files like .zoo/coding.md, .zoo/testing.md, and .zoo/codereview.md when present in the repository.

What is the best way to consolidate per-file review reports into one actionable summary?

Consolidate per-file review reports by aggregating subagent findings into a single deterministic output, validating completeness and providing actionable recommendations with risk labels.

Does automated review work for planning and architectural documents?

Automated review works for planning and architectural documents by applying the same subagent orchestration to files under .zoo/review/, cross-referencing planning docs like .zoo/planning.md.

Are there limitations to using subagents for exhaustive repository reviews?

Exhaustive repository reviews using subagents require files to be placed under the .zoo/review/ directory, limiting the scope of analysis to explicitly designated files within that structure.