codeprobe

Bootstrap the full codeprobe developer experience for a repository, producing `.codeprobe.toml`, `lefthook.yml`, CI workflows, `.claude/plugins/codeprobe/`, GitNexus graph, and a merged `CLAUDE.md` section. Use when the user asks to 'bootstrap a project', 'set up codeprobe', or 'install the codeprobe plugin'. DO NOT use when the repository is already bootstrapped and the drift check passes — use the individual stage commands (`codeprobe init`, `codeprobe ci-init`) for targeted regeneration instead. DO NOT use for interpretation of existing scan results — use codeprobe-interpret.

Generate `.codeprobe.toml` and recommend scanner/tool configuration for a repository based on detected languages, frameworks, and IaC types. Use when the user says 'configure codeprobe', 'what scanners should I use', or 'initialize codeprobe'. DO NOT use when `.codeprobe.toml` already exists and the user has not asked to regenerate or reconfigure it — edit the existing file directly. DO NOT use for running scans — use codeprobe-probe or the `/probe` command.

Generate a comprehensive, cross-linked codebase documentation directory at `.codeprobe/docs/` (33 markdown files across 8 subdirectories, with Mermaid diagrams and source-level citations). Use when the user asks to 'document this codebase', 'generate docs', or 'create documentation'. DO NOT use for single-section updates — pass `--section <name>` or edit the target file directly. DO NOT use if `.codeprobe/heuristic_summary.json` is absent — run `uv run codeprobe index .` first to produce the required artifacts.

Interpret `.codeprobe/scan.sarif` and produce a layered human-readable findings report (Layer 1 dashboard, Layer 2 source explanations, Layer 3 execution flow risk, Layer 4 remediation previews). Use when the user asks to 'interpret scan', 'explain findings', or 'what did the scan find'. DO NOT use when `.codeprobe/scan.sarif` is absent — run codeprobe-probe or `uv run codeprobe scan .` first. DO NOT use for running the scan itself — this skill only reads existing artifacts.

Run `uv run codeprobe scan .` to produce `.codeprobe/scan.sarif` and then hand off to codeprobe-interpret for a layered findings report. Use when the user says 'probe', 'scan and explain', or 'check my code'. DO NOT use for interpretation-only requests when a SARIF file already exists — use codeprobe-interpret directly. DO NOT use if `.codeprobe.toml` is absent and the user has declined bootstrap — run codeprobe-configure or codeprobe-bootstrap first.

Explain the codeprobe trust model and verdict engine (signals, tier escalation, blast-radius thresholds, temporal risk) that produces a `VerdictResponse` with one of {auto_merge, single_review, dual_review, expert_review, block}. Use when the user asks about 'trust model', 'change verdict', or 'when to block a PR'. DO NOT use to compute a verdict for a specific PR — run `uv run codeprobe verdict` (or the CI workflow generated by `codeprobe ci-init`) instead. DO NOT use for general scan interpretation — use codeprobe-interpret.