test-quality

Assess test suites for quality and coverage across CI pipelines.

Updated Nov 11, 2025
One-click install
npx skills add https://github.com/libertininick/chain-reaction --skill test-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-quality
Source: https://github.com/libertininick/chain-reaction/tree/main/.claude/skills/test-quality
Command: npx skills add https://github.com/libertininick/chain-reaction --skill test-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams evaluate software test suites to ensure tests verify substantive functionality and provide meaningful coverage, rather than rubber-stamping code with shallow checks.

Core Features & Use Cases

  • Substantive assertions: Guides tests to prove meaningful behavior and real outcomes instead of trivial non-null checks.
  • True functionality: Emphasizes observable API behavior and contract-level validation over internal state.
  • Edge-case coverage & data variety: Encourages testing boundary conditions with varied, realistic data and inputs.
  • Fixture and mock discipline: Promotes clean fixtures and minimal, purposeful mocks to avoid tight coupling.
  • CI-ready guidance: Provides actionable recommendations for improving test quality in pull requests and pipelines.

Quick Start

Run an analysis on your repository's tests to output a prioritized plan for improving test quality.

Frequently Asked Questions about test-quality

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

FAQPage Schema
How do I assess test suite quality and ensure unit tests prove real behavior?

To assess test suite quality, analyze tests for substantive assertions and true functionality rather than shallow non-null checks. This evaluates whether unit tests verify observable API behavior and contract-level validation, ensuring meaningful coverage.

What makes a test suite provide meaningful coverage instead of rubber-stamping code?

Meaningful coverage requires enforcing checks for edge-case coverage, data variety, and fixture discipline. Tests must validate substantive functionality and real outcomes with varied, realistic data inputs rather than relying on trivial checks.

Can I use test quality assessment for integration and end-to-end tests in CI pipelines?

Yes, test quality assessment is applicable to integration and end-to-end tests across CI pipelines. It enforces checks for test run validity, mock discipline, and substantive assertions during pull request reviews.

How do I improve mock and fixture discipline in my test suites?

To improve mock and fixture discipline, analyze tests to promote clean fixtures and minimal, purposeful mocks. This avoids tight coupling and ensures mocks are used effectively without obscuring true functionality.

What is the best way to evaluate edge-case coverage and boundary conditions in tests?

The best way to evaluate edge-case coverage is to analyze test suites for boundary conditions tested with varied, realistic data. This ensures tests verify substantive functionality across diverse scenarios rather than just typical paths.

Why does my test suite pass CI testing but still fail to catch real bugs?

Test suites pass CI testing but miss real bugs when they lack substantive assertions and edge-case coverage. Analyzing tests for true functionality and observable API behavior reveals shallow checks that rubber-stamp code without validating outcomes.