h4tcher-scoped-audit

What problem does it solve?

It helps you run a bounded, read-only quality audit on a maintainer-defined slice of a repository, producing actionable, severity-graded findings without doing a full 21-domain cycle.

Core Features & Use Cases

• Scoping by intent: Interprets a natural-language scope (single file, small group, subsystem) and resolves it to concrete file paths via globbing.
• Fresh checklist grounded in the rigor contract: Builds a 4–8 item checklist that is explicitly tied back to rigor-contract templates and pillar implications.
• Bounded, safe execution: Enforces a hard ceiling for scope growth and writes only sub-agent artifacts under .audit-workspace/ with a strict no-repo-writes guardrail.
• Severity-graded in-chat reporting: Synthesizes deduped findings into an ≤80-line report including confidence, sources (only for empirical claims), and a recommended next step.

Quick Start

Ask your AI to run a scoped audit for "src/cli/ and related command wiring" and include any key files you consider critical so it can resolve the slice and grade findings by severity.