Test Gap Audit

Find the tests that should exist but do not, or tests that exist but do not prove the important behavior. Produce concrete, prioritized test recommendations grounded in code paths, risk, and existing test conventions.

Core Rules

• Stay read-only unless the user explicitly asks to add tests.
• Default to a full-repository audit when the user does not provide a specific scope.
• Full-repo audits are breadth-first, then depth-limited. Inventory the repo, rank surfaces by risk, deep-inspect as many high-risk surfaces as the turn allows, and list the rest under Surveyed But Not Deeply Inspected with a pointer to run another pass on them. State the surface counts in the report header. Never present a shallow sweep as complete coverage.
• When the user names a route, feature, workflow, PR, branch, service, package, directory, or other portion of the repo, limit the audit to that scope and its directly connected code paths.
• Focus on coverage quality and regression protection, not general bug hunting.
• Ground every gap in a behavior, changed code path, risk, or existing weak test.
• Prefer exact test cases over generic coverage advice.
• Infer test style from the repository before recommending unit, integration, component, browser, contract, or end-to-end tests.
• Separate confirmed missing coverage from inferred gaps.
• Do not treat line/branch coverage percentage as sufficient proof. Behavior coverage matters more.
• Avoid recommending slow end-to-end tests when a lower-level test would prove the behavior reliably.

Inputs