test-review

Automate structured test-coverage reviews and generate _test-review.md findings.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/mcsdodo/kniha-jazd --skill test-review-mcsdodo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-review
Source: https://github.com/mcsdodo/kniha-jazd/tree/main/.claude/skills/test-review-skill
Command: npx skills add https://github.com/mcsdodo/kniha-jazd --skill test-review-mcsdodo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated test-coverage reviews identify gaps, surface missing scenarios, and drive improvements in test quality, reducing risk and rework.

Core Features & Use Cases

  • Structured, two-phase review workflow that surfaces coverage gaps and improvement opportunities.
  • Automatic generation of a dedicated _test-review.md document per target, tracking iterations and decisions.
  • Reusable prompts and templates to guide reviewers through coverage analysis, edge cases, and test quality.
  • Suitable for feature validation, pre-release checks, and ongoing test-health assessments across modules.

Quick Start

Create a {TARGET_DIR}/_test-review.md and run an initial iteration to document coverage gaps.

Frequently Asked Questions about test-review

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

FAQPage Schema
How do I identify test coverage gaps during pre-release checks?

Test coverage gaps are identified by running a structured, multi-iteration review workflow that analyzes modules, surfaces missing scenarios, and aggregates findings into a dedicated markdown tracking document.

What is a structured test-coverage review workflow?

A structured test-coverage review is a deterministic, multi-iteration process applied during feature validation to enforce test quality, document edge cases, and track improvement opportunities per module.

How do I document test health assessments across multiple modules?

You document test health assessments across modules by generating a dedicated `_test-review.md` file in the target directory, which automatically tracks iterations, coverage gaps, and review decisions.

Can I use this test review process for ongoing feature validation?

Yes, you can use this test review process for ongoing feature validation, as it applies reusable prompts and templates to guide reviewers through continuous coverage analysis and edge case discovery.

What's the best way to automate test quality reviews without dependencies?

Automating test quality reviews without dependencies involves a deterministic workflow that creates structured markdown outputs, guiding reviewers through coverage analysis and edge case evaluation.