test-audit

Evaluate test suite quality, coverage, and reliability with risk-weighted metrics.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/blakeox/llm-skills --skill test-audit-blakeox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-audit
Source: https://github.com/blakeox/llm-skills/tree/main/skills/test-audit
Command: npx skills add https://github.com/blakeox/llm-skills --skill test-audit-blakeox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers evaluate the quality, coverage, and effectiveness of their test suites, identifying gaps and potential false confidence.

Core Features & Use Cases

  • Test Suite Analysis: Inventory and evaluate current test frameworks, counts, and runtimes.
  • Risk-based Coverage Review: Prioritize critical modules and their testing adequacy.
  • Gap Identification: Highlight untested behaviors and high-impact paths that need coverage.
  • Test Quality Classification: Distinguish valuable, decoration, false confidence, and obsolete tests to improve reliability.
  • Infrastructure Assessment: Review mocks, fixtures, CI integration, and flakiness to ensure test stability.

Quick Start

Use the test-audit skill to analyze your existing test suite and receive a comprehensive report on test health and recommendations.

Frequently Asked Questions about test-audit

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

FAQPage Schema
How do I evaluate test suite quality and identify false confidence in my codebase?

A test suite audit assesses quality and reliability by inventorying frameworks, measuring risk-weighted coverage metrics, and identifying untested critical paths to eliminate false confidence in your codebase. It distinguishes valuable tests from decoration or obsolete ones.

What is risk-weighted test coverage and how does it prioritize critical modules?

Risk-weighted test coverage prioritizes critical modules by assessing testing adequacy based on production impact rather than raw line counts. This approach identifies untested behaviors and high-impact paths that require immediate attention to ensure robust production quality.

How do I identify untested critical paths and gaps in my integration and e2e testing?

Identifying untested critical paths requires a gap analysis across unit, integration, and e2e testing types to highlight untested behaviors. This process maps high-impact paths and infrastructure weaknesses to guide targeted testing improvements.

Can I assess test infrastructure stability including mocks, fixtures, and CI integration?

Yes, you can assess test infrastructure stability by reviewing mocks, fixtures, CI integration, and test flakiness. This infrastructure assessment ensures test stability and identifies weaknesses that undermine reliable test execution across your project.

What is the best way to classify test quality and distinguish valuable tests from obsolete ones?

The best way to classify test quality is to categorize tests into valuable, decoration, false confidence, and obsolete groups. This classification improves reliability by distinguishing tests that verify critical behaviors from those providing no actual coverage.