spec-coverage-audit

A spec coverage audit identifies gaps between behaviors and tests by extracting behaviors from catalogs under docs/behavior-catalogs and specs under docs/specs, then mapping them to tests by IDs or public API names to classify coverage as covered, partial, none, or N/A.

Auditing fixture realism involves evaluating test data alignment against target behaviors during a spec coverage audit, flagging missing or mismatched fixtures to ensure test data adequately represents the expected behavior scenarios before committing.

Run a spec coverage audit after enumerating behaviors and generating unit tests, or before committing, to verify that every behavior has a test mapping, evaluate fixture realism, and produce a concise audit report guiding fixes.

Yes, the spec coverage audit integrates with review workflows by producing a structured gap analysis report that guides fixes before commits and releases, ensuring traceability across specs, catalogs, and tests.

The audit classifies partial versus none coverage by extracting behaviors from target specs or catalogs and mapping them against existing tests by IDs or public API names to determine if a behavior is fully covered, partially covered, or completely missing.