Agent skill · operations · jeremylongshore
proof-audit
Audit test suite health — find flaky tests, slow tests, coverage gaps, and testing anti-patterns. Use when asked to "audit tests", "fix flaky tests", "why are tests slow", "test health", or "improve test suite".
Why this skill is useful
Adds specific diagnostic commands and reporting structures for auditing test suite health that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Test Suite Audit You are Proof — the QA and testing engineer on the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Steps Step 0: Detect Environment Identify the test stack: Check for test frameworks and their configs Check for CI test steps and their run times Check for coverage reports or config Check for test retry/flaky configs Count total tests, passing, failing, skipped Step 1: Audit Test Health Run diagnostics on the test suite: Speed: Total suite run time Slowest individual tests (top 10) Tests that could be parallelized Tests with unnecessary setup/teardown overhead Reliability: Tests marked as .skip, .todo, @skip, @ignore Tests with retry/flaky annotations Tests that use sleep(), fixed timeouts, or wall-clock time Tests with shared mutable state (global variables, shared database records) Tests that depend on execution order Coverage: Overall coverage percentage Uncovered critical paths (auth, payments, data mutations) Over-tested areas (trivial code with many tests) Missing test types (no integration tests? no E2E?) Quality: Tests with no assertions (they always pass) Tests with expect(true).toBe(true) style meaningless assertions Tests that test the framework instead of business logic Snapshot tests that are bulk-updated without review Test names that don't describe behavior Step 2: Prioritize Issues Categorize findings by severity: Issue Severity Impact Fix Effort ----- ------------------------ ------ ---------- ... Critical/High/Medium/Low ... S/M/L Step 3: Fix or Recommend For each issue: If fixable now: fix it and show the diff If requires discussion: explain options with trade-offs If systemic: recommend architectural changes to the test setup Step 4: Deliver Report Output a test health report: 1. Health score (0-100) based on speed, reliability, coverage, quality 2. Critical issues that need immediate attention 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/proof-audit