test-audit-generator

Audit test suites for path-from-user coverage and test-quality issues.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/chrisdavidmiles/claude-skills --skill test-audit-generator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-audit-generator
Source: https://github.com/chrisdavidmiles/claude-skills/tree/main/skills/test-audit-generator
Command: npx skills add https://github.com/chrisdavidmiles/claude-skills --skill test-audit-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits a codebase’s test suite to reveal whether the tests exercise user-facing paths and catch regressions that matter in production, not just library-level behavior. It helps teams surface path-from-user gaps and identify test smells that undermine confidence in software quality.

Core Features & Use Cases

  • Phase-0 calibration: establish a baseline model of the test suite and its escape hatches.
  • Phase-1 understanding: map entry points, critical paths, and external dependencies.
  • Phase-2 behavior inventory: classify behaviors by criticality, user reachability, and external touchpoints.
  • Phase-3 test audit: identify tautologies, weak assertions, over-mocking, and slice-testing pitfalls.
  • Phase-4 coverage matrix: measure behavior coverage across unit/integration/e2e levels and path-from-user viability.
  • Phase-5 recommendations: delete or rewrite weak tests, add missing end-to-end tests, and tighten processes.
  • Phase-6 honest smell report: surface actionable gaps with evidence-backed rationale.

Quick Start

Run the audit workflow against your repository to generate a complete TEST_AUDIT.md with actionable findings.

Frequently Asked Questions about test-audit-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my test suite for path-from-user coverage?▼

To audit path-from-user coverage, run a phase-driven workflow against your codebase to evaluate whether tests exercise user-facing paths and catch production regressions. It generates a structured report with an escape-hatch inventory and prioritized remediation plan.

Why does my CI pass but production still breaks from test gaps?▼

CI passing while production breaks usually indicates test tautologies, weak assertions, or over-mocking that mask path-from-user gaps. Auditing the test suite reveals these test-quality issues by mapping critical paths and measuring behavior coverage across unit, integration, and e2e levels.

What is path-from-user coverage and how does it differ from regular test coverage?▼

Path-from-user coverage measures whether tests exercise user-facing paths and external dependencies, rather than just library-level behavior. It evaluates critical paths and escape hatches to ensure tests catch regressions that matter in production.

How do I identify weak assertions and tautologies in my test stack?▼

To identify weak assertions and tautologies, perform a behavior inventory classifying behaviors by criticality and user reachability, then audit the tests for tautologies, over-mocking, and slice-testing pitfalls. This produces an honest smell report with evidence-backed rationale.

Can I use this audit for projects with brittle test stacks and unclear coverage?▼

Yes, you can apply this audit to projects with brittle test stacks or unclear coverage. It calibrates a baseline model of the test suite, maps external dependencies, and generates a coverage matrix to measure behavior coverage across unit, integration, and e2e levels.

What are the limitations of auditing test suites for end-to-end coverage?▼

The audit focuses on path-from-user viability and test smells but requires a complete phase-driven workflow from baseline calibration to recommendations. It does not fix tests directly; it produces a prioritized remediation plan to delete, rewrite, or add missing end-to-end tests.