squall-deep-review

Perform structured multi-model code review with an investigation phase.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/DSado88/squall --skill squall-deep-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: squall-deep-review
Source: https://github.com/DSado88/squall/tree/main/.claude/skills/squall-deep-review
Command: npx skills add https://github.com/DSado88/squall --skill squall-deep-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex codebases often hide bugs and security issues that single-model reviews miss. This Skill provides a rigorous, multi-model, investigation-first workflow to surface defects, guaranteeing a thorough, structured assessment before automated reviews.

Core Features & Use Cases

  • Mandatory investigation phase: read targets, map control flow, and form concrete hypotheses before any model calls.
  • Per-model lenses: tailor prompts to investigation findings for each model.
  • Multi-model orchestration: use 3-5 models to balance coverage and reduce blind spots.
  • Synthesis & quality checks: group findings by consensus and cross-reference with initial hypotheses to prioritize fixes.

Quick Start

Run a deep-review on your target codebase by initiating squall-deep-review with the appropriate models and targets.

Frequently Asked Questions about squall-deep-review

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

FAQPage Schema
What is a multi-model deep code review and how does it find security defects?

A multi-model deep code review uses 3-5 different models with tailored prompts to investigate codebases, balancing coverage to reduce blind spots and surface complex security defects that single-model reviews miss.

How do I perform a deep code review on complex and security-sensitive systems?

To perform a deep code review, initiate a mandatory investigation phase to map control flow and form hypotheses, build per-model lenses, then invoke the review with deep enabled, passing investigation context and per-model system prompts.

When should I use an investigation-first code review instead of automated analysis?

Use an investigation-first code review for large codebases, complex systems, and critical security-sensitive code where thorough hypothesis generation and mapping control flow are required before running automated multi-model reviews.

Can I use multiple models to reduce blind spots in my codebase review?

Yes, you can orchestrate 3-5 models with per-model lenses tailored to investigation findings, synthesizing findings by consensus and cross-referencing them with initial hypotheses to prioritize fixes and reduce blind spots.

What are the limitations of using a single-model review for complex systems?

Single-model reviews often miss bugs and security issues hidden in complex codebases, whereas a multi-model approach applies diverse lenses to investigation findings, ensuring a structured assessment that prioritizes fixes by consensus.