Run before modifying any function. Shows what breaks, what tests cover it, and what to check.

Fully self-contained setup for cqs in a new project. After running this, the project has semantic search, notes, continuity tracking, and all skills working.

Run after making changes, before committing. Reviews your diff for impact and risk.

Unified cqs CLI dispatcher — semantic code search, call graph navigation, impact analysis, quality tools, notes, and infrastructure. Use `/cqs <command> [args]` for any cqs operation.

Execute multiple cqs queries in a single persistent session via stdin batch mode.

Task planning with scout data + task-type templates. Produces implementation checklists.

Review, prune, and suggest notes in notes.toml. Cleans stale notes and proposes new ones from recent changes.

Adversarial security audit — attacker mindset, PoC-required, end-to-end attack chains.

Guided diagnosis of common cqs issues. Run through checks in order, stop at first problem found.

Update PROJECT_CONTINUITY.md and notes.toml with current session state. Use proactively before context compaction or when switching tasks.