skills.rest
Hatedatastructures
HatedatastructuresCOMMUNITY
Explore all skills by this author →
GitHub

review-test

Evaluate test coverage for code changes and identify missing or shallow tests.

5|1|Updated Dec 14, 2025
Search Tags:#coverage#mocking#quality-assurance#code-review#integration-tests#test-review
One-click install
npx skills add https://github.com/Hatedatastructures/Prism --skill review-test-hatedatastructures
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-test
Source: https://github.com/Hatedatastructures/Prism/tree/main/.claude/skills/review-test
Command: npx skills add https://github.com/Hatedatastructures/Prism --skill review-test-hatedatastructures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you judge whether code changes are backed by adequate tests, so you can catch missing coverage, weak assertions, and fragile test design before merge.

Core Features & Use Cases

  • Change-to-test mapping: Matches each changed function, class, module, or config field to the tests that should cover it.
  • Depth review: Checks happy paths, boundary cases, error handling, concurrency, protocol flows, and mock quality.
  • Quality verdicts: Produces actionable review notes for pull requests, pre-merge checks, and periodic test health audits.

Quick Start

Ask the Skill to review the changed files and summarize test coverage gaps, weak test cases, and required follow-up tests.

Frequently Asked Questions about review-test

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

FAQPage Schema
How do I identify missing test coverage for code changes before merging a pull request?▼

To identify missing test coverage, map changed functions, classes, and config fields to existing tests, then check assertions, error paths, and concurrency to find shallow or low-quality tests before merge.

What is the best way to review test quality for protocol handlers and configuration changes?▼

Reviewing test quality for protocol handlers and configuration changes involves checking happy paths, boundary cases, error handling, and mock quality to produce actionable review notes for pre-merge validation.

How do I map changed behavior to existing tests during a code review?▼

Mapping changed behavior to existing tests requires matching each modified module, function, or config field against its corresponding test cases to verify coverage depth and uncover fragile test design.

Does test review work for ongoing test health assessments across large modules?▼

Test review works for ongoing test health assessments by evaluating coverage depth, weak assertions, and missing error paths across modules to ensure long-term test suite reliability and quality assurance.

How do I check weak assertions and mock quality in integration tests?▼

Checking weak assertions and mock quality in integration tests requires evaluating whether test cases validate boundary conditions, concurrency, and protocol flows instead of merely executing happy paths without strict assertions.

Related Skills

Explore More Software Engineering Skills→
noise-xyznoise-xyz
9

brane-impact

Analyze Brane SDK code changes to identify affected modules and tests.

Official
Advanced
sunholo-datasunholo-data
33

Test Coverage Guardian

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

Community
Intermediate
pdylanrosspdylanross
1

unit-testing-patterns

Enforce unit testing best practices for structure, mocking, and assertions.

Community
Intermediate
StrategicMilkStrategicMilk

Test Coverage Analysis

Identify untested code paths and generate test specifications with a JSON report.

Community
Advanced