testing-reviewer

Identifies test quality gaps and false confidence risks in code diffs.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ybbms777/compound-engineering --skill testing-reviewer-ybbms777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-reviewer
Source: https://github.com/ybbms777/compound-engineering/tree/main/skills/agent-testing-reviewer
Command: npx skills add https://github.com/ybbms777/compound-engineering --skill testing-reviewer-ybbms777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often miss critical test quality issues that lead to undetected regressions, including false confidence from vacuous tests, brittle tests that break on harmless refactors, and untested error paths that fail in production.

Core Features & Use Cases

  • Test Coverage Gap Detection: Identifies untested branches in new code, missing edge case coverage for error paths, and behavioral changes with no corresponding test additions.
  • False Confidence Flagging: Catches tests that only assert no errors are thrown, assert truthiness instead of specific values, or mock so heavily that they verify mock behavior instead of actual code functionality.
  • Brittle Test Identification: Spots implementation-coupled tests that break during refactors when no behavior has changed, such as tests asserting exact mock call counts or testing private methods directly. Use Case: When reviewing a PR that adds new error handling logic for an API call, this Skill will flag if no tests cover the error path, or if existing tests only mock the error throw instead of verifying the fallback behavior works correctly.

Quick Start

Use the testing-reviewer skill to evaluate the test coverage and quality of the code changes in the current pull request.

Frequently Asked Questions about testing-reviewer

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

FAQPage Schema
How do I detect untested code branches during a code review?

Detect untested code branches during code review by analyzing pull request diffs to find new logic paths lacking corresponding test additions, ensuring behavioral changes are validated rather than relying on false security.

What is a vacuous assertion in test suites and how does it create false confidence?

A vacuous assertion in test suites creates false confidence by only asserting no errors are thrown or checking truthiness instead of specific values, meaning the test passes without validating actual code functionality or catching regressions in the new behavior.

How do I identify brittle tests that break during refactoring?

Identify brittle tests that break during refactoring by spotting implementation-coupled tests, such as those asserting exact mock call counts or testing private methods directly, which fail when harmless structural changes occur even if no behavior has changed.

Can I check if my pull request is missing error path test coverage for API calls?

Yes, you can check for missing error path test coverage by evaluating code diffs in a pull request. The review flags new error handling logic for API calls if no tests verify the fallback behavior works correctly when an error is thrown.

Why do heavily mocked tests fail to verify actual code functionality?

Heavily mocked tests fail to verify actual code functionality because they mock so extensively that they end up verifying the mock behavior itself rather than the real code, leading to false confidence that regressions are caught.