test-review

Analyze test suites for anti-patterns, coverage gaps, and quality risks.

4|1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/nntan90/qa-skill-suite --skill test-review-nntan90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-review
Source: https://github.com/nntan90/qa-skill-suite/tree/main/test-review
Command: npx skills add https://github.com/nntan90/qa-skill-suite --skill test-review-nntan90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review test suites for quality issues, anti-patterns, and coverage gaps. Load when asked to review tests, audit test quality, find bad tests, detect anti-patterns, check if tests are trustworthy, verify test coverage is real (not fake), or analyze whether a test suite actually protects the codebase. Identifies: false positives, brittle tests, missing assertions, non-independent tests, tautological tests, and coverage theater. Also acts as "verification-before-completion" gate — forces validation of test completeness before declaring a feature done.

Core Features & Use Cases

  • Anti-pattern detection across unit, integration, and UI tests
  • Coverage quality assessment and false-positives detection
  • Verification-before-completion gate to ensure tests are complete before feature done
  • Structured output with a completeness and risk assessment

Quick Start

Run the qa/test-review skill on your test suite to generate a comprehensive quality report.

Frequently Asked Questions about test-review

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

FAQPage Schema
How do I audit my test suite for anti-patterns and false positives?

To audit a test suite for anti-patterns and false positives, you can run a test review process that identifies brittle tests, missing assertions, and non-independent tests. This generates a structured quality report with a findings table and coverage score.

What is coverage theater in test quality assurance?

Coverage theater in test quality assurance refers to tests that appear to provide coverage but actually fail to protect the codebase. A test audit detects this by surfacing tautological tests and false positives, verifying that your test suite is genuinely trustworthy.

How do I check if my unit and integration tests are brittle before feature completion?

You can check unit and integration tests for brittleness by applying a verification-before-completion gate. This scans for non-independent tests and anti-patterns, producing a completion-gate verdict to ensure tests are complete before declaring a feature done.

Can I detect missing test cases across different programming languages?

Yes, you can detect missing test cases across different programming languages by running a test quality audit. The process analyzes unit, integration, and end-to-end tests to surface coverage gaps and outputs a list of missing test cases.

What is the best way to find tautological tests in an existing codebase?

The best way to find tautological tests is to execute a test review scan across your test suite. This anti-pattern detection mechanism evaluates test logic and assertions, highlighting tautological tests in a structured findings table.

Does test review work for end-to-end UI tests or only unit tests?

Test review works for end-to-end UI tests as well as unit and integration tests. The audit scans across all these test types to identify quality risks, coverage gaps, and anti-patterns, providing a comprehensive overall quality assessment.