zoo-code-review

Review Zoo code changes for correctness, regression safety, and test coverage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline and enforce rigorous evaluation of Zoo code changes to catch defects, regressions, and coverage gaps before merge.

Core Features & Use Cases

  • Evidence-driven reviews: identify concrete issues with file/line references and severity.
  • Non-editing workflow: review-only posture that does not modify code, but directs fixes.
  • Scope coverage: applies to Zoo workflows across code, tests, and documentation to prevent regressions.

Quick Start

Review the Zoo change set and provide concrete findings with evidence, prioritized by impact, and suggested fixes.

Frequently Asked Questions about zoo-code-review

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

FAQPage Schema
How do I perform a Zoo code review to prevent regressions?

Perform a Zoo code review by evaluating change proposals for correctness, regression safety, and test coverage, generating reviewer-ready notes with file/line references, severity, and steps to validate fixes.

What is evidence-driven code review for change management?

Evidence-driven code review is a process that identifies concrete issues with file and line references, prioritizes them by severity and impact, and provides concrete steps to reproduce and validate fixes without editing code.

Can I use a review-only workflow to direct code fixes without modifying files?

Yes, a review-only workflow evaluates Zoo code changes without modifying code directly, instead directing fixes through evidence-backed findings and prioritized reviewer-ready notes.

Does the code review process cover tests and documentation or just source code?

The code review process covers Zoo workflows across source code, tests, and documentation to comprehensively prevent regressions and ensure maintainability before merge.

What's the best way to prioritize code defects found during a change review?

Prioritize code defects found during a change review by assessing their impact on correctness and regression safety, then categorizing findings by severity with concrete steps to reproduce and validate fixes.

When should I not use an automated review approach for code changes?

Avoid using an automated review approach when a change proposal lacks clarity or alignment with Zoo workflows, as the review relies on assessing maintainability and concrete evidence to produce valid findings.