vibelisted

# Vibe Skill > **Purpose:** Is this code ready to ship? Three steps: 1. **Complexity analysis** — Find hotspots (radon, gocyclo) 2. **Bug hunt audit** — Systematic sweep for concrete bugs 3. **Council validation** — Multi-model judgment --- ## Quick Start ```bash $vibe # validates recent changes $vibe recent # same as above $vibe src/auth/ # validates specific path $vibe --quick recent # fast inline check, no agent spawning $vibe --deep recent # 3 judges instead of 2 $vibe --sweep recent # deep audit: per-file explorers + council $vibe --mixed recent # cross-vendor (Claude + Codex) $vibe --preset=security-audit src/auth/ # security-focused review $vibe --explorers=2 recent # judges with explorer sub-agents $vibe --debate recent # two-round adversarial review ``` --- ## Execution Steps **Project reviewer config:** If `.agents/reviewer-config.md` exists, its full config (`reviewers`, `plan_reviewers`, `skip_reviewers`) is passed to council for judge selection. See `$council` Step 1b. ### Crank Checkpoint Detection Before scanning for changed files via git diff, check if a crank checkpoint exists: ```bash if [ -f .agents/vibe-context/latest-crank-wave.json ]; then echo "Crank checkpoint found — using files_changed from checkpoint" FILES_CHANGED=$(jq -r '.files_