review-tests

Name: review-tests
Availability: InStock
Author: cesau78

Reviews changed-behavior tests for gaps, brittleness, and missing coverage across frontend/backend codebases.

Updated Apr 2, 2026

Search Tags:#quality #review #coverage #tests #diff-analysis #brittleness

Ready to run

npx skills add https://github.com/cesau78/cesau-skills --skill review-tests-cesau78

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-tests
Source: https://github.com/cesau78/cesau-skills/tree/main/review-tests
Command: npx skills add https://github.com/cesau78/cesau-skills --skill review-tests-cesau78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews tests for gaps, brittleness, and missing coverage for changed behavior. Use when test files or implementation under test changed, before push, or when skills-advisor recommends this lens or the user asks for a test review.

Core Features & Use Cases

Identify coverage gaps in tests that relate to changed behavior, including edge cases.
Detect brittleness in tests, such as brittle assertions, flaky mocks, or over-constrained expectations.
Provide actionable recommendations to improve test quality and coverage across frontend and backend codebases.

Quick Start

Run a diff-driven review to surface gaps, brittleness, and missing coverage.

Frequently Asked Questions about review-tests

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

FAQPage Schema

How do I identify coverage gaps in tests for changed behavior before pushing?▼

To identify coverage gaps in tests for changed behavior, run a diff-driven review that analyzes touched test files and implementation code. This process evaluates behavioral coverage over simple line counts and outputs a structured assessment with actionable recommendations to fix missing edge cases.

What is test brittleness and how do I detect flaky mocks or brittle assertions?▼

Test brittleness refers to fragile tests with flaky mocks, brittle assertions, or over-constrained expectations that fail unpredictably. You detect test brittleness by evaluating test suites against changed behavior, which surfaces these structural weaknesses and provides recommendations to improve overall test quality.

Does this test review approach work for both frontend and backend codebases?▼

Yes, this test review approach works across both frontend and backend codebases. It evaluates test suites touched by diffs or behavioral changes regardless of the stack, focusing on behavioral coverage, brittleness detection, and quality improvements for the changed implementation.

When do I need to run a behavioral test coverage analysis?▼

You need to run a behavioral test coverage analysis when test files or implementations under test change, specifically before pushing code. It is also recommended when seeking a test review to ensure new behavior is properly covered and existing tests are not brittle.

How do I review tests for missing edge cases related to recent diffs?▼

Review tests for missing edge cases by applying a diff-driven analysis to changed behavior. This method identifies gaps in coverage and brittleness across affected test suites, outputting a structured assessment with actionable recommendations to improve test quality before push.