probe

name	probe
description	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.
allowed-tools	Bash Read Grep Glob

Run a full codeprobe scan on the current repository and interpret the results.

Steps

1. Run uv run codeprobe scan . to produce SARIF output at .codeprobe/scan.sarif
2. Load the interpret skill to analyze and explain the findings
3. Present a structured report with findings, risk hotspots, and recommended actions

Notes

• If the scan fails, run uv run codeprobe check first to verify tool availability
• To scan only specific scanners, use uv run codeprobe scan . --scanners ruff,ty,semgrep
• The SARIF file is written to .codeprobe/scan.sarif by default
• If .codeprobe/heuristic_summary.json exists (from codeprobe index), the interpretation will be richer

Acceptance

Success = .codeprobe/scan.sarif exists with at least one runs[] entry, the codeprobe-interpret skill's Layer 1 dashboard was rendered to the user, and the final report closes with a prioritized punch list of recommended actions.