ze-review-deep

Review Ze repository changes across security, concurrency, errors, tests, logic, data flow, API compatibility, rules, and docs.

50|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/ze-software/ze --skill ze-review-deep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ze-review-deep
Source: https://github.com/ze-software/ze/tree/main/.codex/skills/ze-review-deep
Command: npx skills add https://github.com/ze-software/ze --skill ze-review-deep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when working in the Ze repo and the user asks for ze-review-deep or for an exhaustive review across multiple lenses. Review the selected scope for security, concurrency, errors, tests, logic, data flow, API compatibility, rule compliance, and docs; use parallel sub-agents only when the user explicitly asks for parallel review.

Core Features & Use Cases

  • Multi-lens scope: Reviews across security, concurrency, error handling, tests, logic, data flow, API compatibility, rules, and docs.
  • Scoped execution: Operates on a specific working tree, path, or branch diff and aggregates results.
  • Parallel review (optional): Uses parallel sub-agents only when the user explicitly requests parallel review, otherwise runs lenses sequentially.
  • Unified findings: Merges lens results into a single severity-ordered report, with notes on skipped or timed-out lenses.

Quick Start

Use this workflow to initiate an exhaustive Ze change review by specifying the scope; the system will coordinate the relevant lenses and return a unified report.

Frequently Asked Questions about ze-review-deep

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

FAQPage Schema
How do I run a comprehensive code review across security, concurrency, and data flow in my repository?

A comprehensive code review across security, concurrency, and data flow analyzes repository changes through multiple lenses. It evaluates the working tree or branch diff, aggregating findings into a single severity-ordered report to highlight critical issues.

What is the best way to review branch diffs for API compatibility and error handling?

Reviewing branch diffs for API compatibility and error handling involves applying a multi-lens analysis to the changed scope. This process inspects data flow and logic rules, returning concrete, severity-ordered findings to ensure robust integration.

Can I use parallel sub-agents for multi-lens code analysis on a specific path?

Yes, parallel sub-agents can execute multi-lens code analysis on a specific path. When explicitly requested for parallel review, the system coordinates concurrent lens checks, otherwise it runs them sequentially to aggregate unified findings.

Does multi-lens code review cover test coverage and documentation compliance?

Multi-lens code review covers test coverage and documentation compliance by inspecting repository changes. It evaluates the selected working tree scope against rule and documentation lenses, merging the results into a unified severity-ordered report.

What are the limitations when executing multi-lens code analysis on large working trees?

When executing multi-lens code analysis on large working trees, limitations include potential lens timeouts. The system addresses this by noting any skipped or timed-out lenses within the final unified severity-ordered report to maintain transparency.