skills.rest
Andreicr1
Andreicr1COMMUNITY
Explore all skills by this author →
GitHub

testing-reviewer

Evaluate code diffs for test coverage and behavioral verification.

Updated Mar 14, 2026
Search Tags:#edge-cases#assertions#test-coverage#testing-strategy#code-diff#test-review#brittle-tests
One-click install
npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill testing-reviewer-andreicr1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-reviewer
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/testing-reviewer
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill testing-reviewer-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You evaluate whether tests in a diff prove the code works rather than merely existing. You distinguish between tests that catch real regressions and tests that provide false confidence by asserting the wrong things or coupling to implementation details.

Core Features & Use Cases

  • Untested branches in new code: Identify new conditional paths that lack corresponding tests and trace them to ensure coverage.
  • False confidence tests: Flag tests that merely assert non-throwing or truthiness instead of validating behavior.
  • Brittle tests: Detect tests tightly coupled to implementation details, including exact mock call counts or order dependencies, and suggest robust alternatives.
  • Edge-case and error-path coverage: Highlight missing tests for error handling, fallback logic, and exceptional scenarios.
  • Diff-to-test mapping: Provide actionable recommendations to align diffs with test suites and improve overall confidence.

Quick Start

Review the latest diff and clearly report any untested branches, brittle tests, and missing error-path coverage.

Frequently Asked Questions about testing-reviewer

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

FAQPage Schema
How do I review a code diff to identify false confidence tests?▼

Review tests for false confidence by evaluating whether they assert non-throwing states or truthiness rather than validating actual behavior changes in the diff. This distinguishes tests catching real regressions from those providing false confidence.

What are brittle tests and how do I detect them during code review?▼

Detect brittle tests during code review by flagging tests tightly coupled to implementation details, including exact mock call counts or order dependencies, and suggesting robust alternatives that verify behavior.

How do I find untested branches and missing edge-case coverage in new code?▼

Find untested branches and missing edge-case coverage by tracing new conditional paths in the code diff to ensure they have corresponding tests. Highlight missing tests for error handling, fallback logic, and exceptional scenarios to improve overall confidence.

Does this test review approach work for refactoring and bug fixes?▼

Yes, this test review approach works for refactoring and bug fixes. It applies to code changes across new features, bug fixes, and refactors, specifically assessing branch coverage and behavior verification to ensure tests prove the code works.

What is the best way to map test suites to code diffs?▼

The best way to map test suites to code diffs is to provide actionable recommendations that align the diffs with the test suites. This ensures behavioral changes are accompanied by test updates and improves overall coverage confidence.

Why should I avoid implementation-coupled tests in my testing strategy?▼

Avoid implementation-coupled tests in your testing strategy because they are brittle and provide false confidence. Tests tightly coupled to exact mock call counts break easily during refactoring and fail to verify actual behavior.

Related Skills

Explore More Software Engineering Skills→
speednet-softwarespeednet-software
21

code-review-test-analyzer

Analyze code changes to identify critical gaps in test coverage.

Official
Advanced
skyosevskyosev
5

test-hunter-go

Analyze Go test suites for coverage gaps, brittle tests, and implementation-coupled assertions.

Community
Advanced
afel6afel6

test-driven-development

Write failing tests before production code and run test suites to prevent regressions.

Community
Advanced
sunholo-datasunholo-data
33

Test Coverage Guardian

Analyze test coverage to identify gaps, dead code, and brittleness.

Community
Intermediate