Test Gap Finder

The problem

High code coverage percentages often mask critical missing tests for edge cases, race conditions, and security boundaries. Developers frequently ship features that pass CI but fail in production due to untested failure paths or tenant isolation leaks.

What it does

• Analyzes code changes and PR diffs against existing test suites to find behavioral gaps.
• Maps implementation logic to a behavior-to-test matrix to identify unprotected state transitions.
• Audits coverage for high-risk areas including concurrency, retries, rollbacks, and cross-tenant permissions.
• Provides a prioritized list of specific test recommendations categorized by severity (Critical to Low).
• Calculates a 100-point test evidence score and issues a release-readiness verdict.

Frameworks & tools

Works with any testing framework including Jest, Vitest, Playwright, Pytest, and JUnit. Compatible with unit, integration, contract, and E2E test suites.

Why this beats prompting it yourself

General LLM prompts often miss subtle infrastructure risks like dead-letter routing or idempotent retries. This skill follows a 24-step audit workflow that forces inspection of boundary conditions and integration assumptions that standard coverage tools ignore.

Use cases

• Reviewing a PR to ensure a bug fix includes a valid regression test.
• Identifying missing permission checks before deploying multi-tenant API changes.
• Finding shallow assertions that provide false confidence without verifying side effects.
• Determining if a complex data migration has sufficient rollback and integrity tests.

Known limitations

Does not execute code or run tests locally. Analysis is based purely on provided implementation files, diffs, and test code.