test-evidence-review

Validate game test files and manual evidence against story acceptance criteria.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill test-evidence-review-xganqaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/test-evidence-review
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill test-evidence-review-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents story closure from happening with tests or manual evidence that merely exist, by assessing whether automated coverage and required sign-offs actually support the acceptance criteria.

Core Features & Use Cases

  • Automated test quality review: Detects vacuous tests (0 assertions), thin coverage (low assertion density), weak edge-case coverage, generic naming, and missing formula traceability.
  • Manual evidence quality review: Checks criterion linkage, required sign-offs, artefact completeness (screenshots/walkthroughs), and freshness relative to sprint timing.
  • Verdict-driven reporting: Produces a per-story ADEQUATE/INCOMPLETE/MISSING result and flags BLOCKING vs ADVISORY issues for QA sign-off workflows.

Quick Start

Run /test-evidence-review sprint to review all stories in the current sprint and generate a quality verdict report.

Frequently Asked Questions about test-evidence-review

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

FAQPage Schema
How do I validate test coverage for story acceptance criteria?

Test coverage validation checks if automated tests and manual evidence sufficiently support acceptance criteria. This Skill evaluates assertion density, edge-case coverage, and evidence linkage to output ADEQUATE, INCOMPLETE, or MISSING verdicts for sign-off workflows.

What is evidence readiness review in QA workflows?

Evidence readiness review assesses whether manual evidence documents and automated tests provide sufficient coverage for story closure. It checks criterion linkage, required sign-offs, artefact completeness, and freshness relative to sprint timing to prevent premature story closure.

How do I detect vacuous tests with zero assertions?

Detecting vacuous tests involves analyzing assertion density and coverage heuristics in test files. This Skill identifies tests with zero assertions, thin coverage, weak edge-case handling, and generic naming to flag BLOCKING or ADVISORY issues in QA readiness reports.

Can I review test evidence across an entire sprint?

Sprint-wide test evidence review supports single-story, sprint, or system-wide checks across Logic, Integration, Visual/Feel, UI, and Config/Data story types. Running a sprint review generates per-story quality verdicts with blocking issue flags.

What is the best way to check required sign-offs and artefact freshness?

Checking required sign-offs and artefact freshness involves evaluating manual evidence documents against sprint timing and completeness criteria. This Skill validates criterion linkage, screenshots, walkthroughs, and freshness to produce BLOCKING or ADVISORY issue flags.

Why does my story closure fail despite having existing tests?

Story closure fails when tests merely exist without sufficient assertion coverage or evidence linkage. This Skill prevents closure by assessing whether automated coverage and required sign-offs actually support acceptance criteria, flagging INCOMPLETE or MISSING verdicts.