test-audit

Audits test files against Q1-Q25 quality gates and AP1-AP32 anti-patterns with tiered scoring.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Test suites often contain weak assertions, phantom mocks, orphan tests, and untested public methods that give false confidence in coverage. This Skill systematically audits unit and integration test files against a 25-question quality checklist and a 32-item anti-pattern catalog, producing tiered scores (A/B/C/D) that reveal which tests are trustworthy and which need rewriting. ## Core Features & Use Cases - Batch quality scoring: Evaluates test files against Q1-Q25 gates covering assertions, mocks, branch coverage, and isolation, with critical gates (Q7, Q11, Q13, Q15, Q17) enforcing a Tier C floor on failure. - Anti-pattern detection: Detects 32 anti-patterns including zero-assertion tests, tautological mocks, committed focus markers, and flake-masking retries, with automatic Tier-D classification for red flags. - Coverage and backlog integration: Updates a coverage registry, persists findings to a backlog with deduplication, and supports an optional post-audit fix workflow. - Use Case: After mass-generating tests for a release, run the audit across the project to find files with phantom mocks and untested public methods, then get a prioritized rewrite queue before shipping. ## Quick Start Ask the assistant to run zuvo:test-audit on the project or a specific test file to get a tiered quality report with scores and fix recommendations.

Frequently Asked Questions about test-audit

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

FAQPage Schema
How do I audit test quality across an entire project?

Run the audit with the 'all' argument to evaluate every test file in the project against the Q1-Q25 checklist and AP anti-pattern catalog. Files are batched into groups of 8-10, scored by tier, and aggregated into a summary report saved under zuvo/audits/.

What test anti-patterns does the audit detect?

It detects 32 anti-patterns including zero-assertion tests, tautological mocks, duplicate test names, hardcoded waits, committed focus markers like it.only, and flake-masking retries. Red flags such as AP13, AP16, and AP31 trigger automatic Tier-D classification.

Does the test audit work with pytest, Go, or Rust tests?

Yes, the checklist applies across languages, with stack-specific tools for Python, Kotlin, PHP, and frameworks like Django and FastAPI. Language-specific items such as AP25 are marked N/A where pytest, Go, or Rust have no equivalent.

Can I audit a single test file or exclude E2E tests?

Passing a file path forces deep mode with full evidence for that file, and multiple files can be listed space-separated. E2E tests are excluded by default and only included when the --include-e2e flag is set.

What happens if CodeSift tools are unavailable during the audit?

The audit falls back to standard find, Read, Grep, and Glob commands for file discovery and production pairing. Analysis is slower and production file pairing relies on path conventions instead of symbol resolution.

When should I not use the test audit skill?

It is not for single-file code review, writing new tests, or fixing anti-patterns across many files; those belong to the review, write-tests, and fix-tests skills respectively. Use --read-only when you want a report without coverage or backlog writes.