comprehensive-review

Automate four-wave code reviews with per-package and adversarial analysis.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/seanyofthedead/omaha-oracle --skill comprehensive-review-seanyofthedead
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comprehensive-review
Source: https://github.com/seanyofthedead/omaha-oracle/tree/main/.claude/skills/comprehensive-review
Command: npx skills add https://github.com/seanyofthedead/omaha-oracle --skill comprehensive-review-seanyofthedead

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gopls, Context7, sonnet, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of in-depth code reviews, streamlining the assessment of large or high-risk changes through a four-wave review process.

Core Features & Use Cases

  • Four-Wave Review: Performs a thorough review process with four distinct waves, each focusing on different aspects of code quality.
  • Per-Package Deep Analysis: Wave 0 reviews individual packages to identify issues that require a deeper understanding of the codebase.
  • Cross-Cutting Analysis: Wave 1 conducts a broad, parallel review across multiple packages, focusing on foundational aspects of code quality.
  • Targeted Deep-Dive Review: Wave 2 builds on Wave 1 findings with a more focused analysis of specific areas.
  • Adversarial Review: Wave 3 introduces adversarial reviewers to challenge consensus and uncover missed risks.
  • Automated Fixing: Capable of auto-fixing issues unless in review-only mode.

Quick Start

Run the /comprehensive-review command to initiate a comprehensive code review on the current diff or PR.

Frequently Asked Questions about comprehensive-review

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

FAQPage Schema
How do I automate an in-depth code review for large changes?▼

Automate an in-depth code review by running a multi-wave process with per-package analysis, cross-cutting reviews, and adversarial challenges to thoroughly assess large code changes.

What is an adversarial code review and how does it improve quality?▼

An adversarial code review introduces reviewers that challenge consensus to uncover missed risks, ensuring high-risk changes are scrutinized beyond standard automated checks.

Do I need gopls and Context7 to run this automated review?▼

Yes, the automated review requires tools like gopls and Context7 to perform deep per-package analysis and gather contextual understanding across the codebase.

Can I run a multi-wave code review without automatically fixing issues?▼

Yes, you can run a multi-wave code review without auto-fixing by using review-only mode, restricting the process to analysis and reporting without modifying the code.

What is the best way to review cross-cutting concerns across multiple packages?▼

The best way to review cross-cutting concerns is using a parallel review wave that focuses on foundational code quality aspects across multiple packages simultaneously.