deep-dive

Audits codebase scope with parallel explorer waves, dual reviewers, and critic challenges.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/pandejesal/drone-nav-sar --skill deep-dive-pandejesal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-dive
Source: https://github.com/pandejesal/drone-nav-sar/tree/main/.swarm/bundled-skills/deep-dive
Command: npx skills add https://github.com/pandejesal/drone-nav-sar --skill deep-dive-pandejesal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual code audits are slow, inconsistent, and prone to unverified findings. This Skill runs a structured, read-only deep audit of any codebase scope, producing verified findings with severity ratings instead of ad-hoc observations. ## Core Features & Use Cases - Parallel Explorer Waves: Dispatches up to 8 lane-based explorer missions (security, UX, architecture, performance, and more) that partition the scope into non-overlapping file sets with full coverage guarantees. - Two-Stage Verification: Every candidate finding is verified or rejected by 2 parallel reviewers, then HIGH/CRITICAL findings survive sequential critic challenges for false positives and severity accuracy. - Profile-Based Audits: Choose standard, security, ux, architecture, or full profiles to activate only the relevant audit lanes. - Use Case: Before a major release, run a security-profile deep dive on your authentication module to receive a report of verified vulnerabilities with evidence, severity, and recommended remediation phases. ## Quick Start Ask the architect to run a deep dive audit on a specific scope, for example: run a deep dive on the payment flow with the security profile.

Frequently Asked Questions about deep-dive

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

FAQPage Schema
How do I run a deep code audit on a specific module?

Emit a MODE: DEEP_DIVE header with the scope (e.g., "auth" or "src/hooks/"), a profile (standard, security, ux, architecture, or full), and optional caps on explorer count. The protocol maps the scope, dispatches parallel explorer lanes, and returns a verified findings report.

What audit profiles does the deep-dive protocol support?

Five profiles are supported: standard, security, ux, architecture, and full. Each profile activates specific audit lanes such as SECURITY_TRUST for security or UX_FLOW for ux, while the full profile activates all eight lanes.

Does the deep-dive audit modify my source code?

No. The protocol is strictly read-only: it never mutates source code, never delegates to a coder agent, and never creates files outside the .swarm/ directory. It only reads, analyzes, and reports findings.

How are audit findings verified before appearing in the report?

Explorers emit only unverified candidate findings. Two parallel reviewers then verify or reject each candidate, and HIGH/CRITICAL findings additionally survive two sequential critic challenges covering false positives and severity accuracy.

What happens when an explorer lane fails during an audit?

Failed lanes are retried up to two times with different parameters, then replaced with an equivalent dispatch mechanism as a fallback. If no equivalent exists, the audit stops and reports the coverage gap as BLOCKED rather than producing a degraded review.