analyzelisted

<!-- prettier-ignore-start --> **Document Version:** 2.0 **Last Updated:** 2026-04-15 **Status:** ACTIVE <!-- prettier-ignore-end --> **Shared conventions:** See `.claude/skills/shared/CONVENTIONS.md` Also supports: `--type`, `--depth`, `--synthesize`. # Analyze The front door to the Content Analysis System. One command for everything: `/analyze <anything>`. ## Critical Rules (MUST) 1. **MUST keep the router thin** — all analysis logic lives in handler skills; this router only detects type, dispatches, and updates the index. 2. **MUST update the index** after every successful analysis (see REFERENCE §5 — Index Update Procedure). 3. **MUST pass unknown flags through** to the handler unchanged (see REFERENCE §2.4 — Flag Passthrough). 4. **MUST stop and ask on ambiguous input** — never guess; follow the numbered resolution protocol (see REFERENCE §6.1 — Ambiguous Input Resolution). 5. **MUST validate handler artifacts** before running `update-index.js` (see Router Flow Step 4.5). 6. **MUST sanitize all error messages** via `scripts/lib/sanitize-error.js` per CLAUDE.md §5 Top 5 Anti-Patterns. 7. **SHOULD log routing decisions** to `.claude/state/analyze-routing-log.jsonl` (one JSON object per line) for future detection tuning. ## When to Use - User invokes `/analyze` with any URL, file path, or no input - Need to route a source through CAS without knowing its type upfront - Need cross-source synthesis without specifying a scope - Want indexed results