review-tests

To verify your test suite catches real bugs, run a mutation testing audit that intentionally breaks production code to confirm tests fail. This skill generates targeted break mutations for developer-run verification against acceptance criteria.

Mutation testing is an auditing technique that introduces targeted code breaks to check if tests detect regressions. You need it after shipping a feature to validate that acceptance criteria for auth, data writes, and error handling paths are genuinely exercised.

You audit test coverage against acceptance criteria by generating a coverage table that marks happy paths and failure paths as strong, missing, or weak. This skill compares your tests directly to each specified criterion to identify gaps.

Yes, you can evaluate test isolation, specificity, realistic inputs, and edge-case coverage using a test quality rubric. The skill scores these dimensions, then returns a letter-grade summary with prioritized action items for fixes.

The best way to check if error handling and permission logic are tested is to propose specific break-the-code mutations for those paths. Developers run these mutations to confirm whether tests genuinely detect regressions in auth and data write logic.

Your test suite always passes because tests may not assert the correct behavior, leading to false positives. A test audit with mutation checks intentionally breaks error handling code to expose whether your tests genuinely fail when regressions occur.