test-evidence-review

Review test files and evidence documents to produce ADEQUATE, INCOMPLETE, or MISSING verdicts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JunnnnyWon/Codex-Game-Studios --skill test-evidence-review-junnnnywon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/JunnnnyWon/Codex-Game-Studios/tree/main/.claude/skills/test-evidence-review
Command: npx skills add https://github.com/JunnnnyWon/Codex-Game-Studios --skill test-evidence-review-junnnnywon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quality review of test files and manual evidence documents. Goes beyond existence checks — evaluates assertion coverage, edge case handling, naming conventions, and evidence completeness. Produces ADEQUATE/INCOMPLETE/MISSING verdict per story. Run before QA sign-off or on demand.

Core Features & Use Cases

  • Parse argument scopes (single story, sprint, system) to identify stories in scope.
  • Locate test and evidence files across unit/integration/QA artifacts.
  • Evaluate automated test quality (assertions, edge cases, naming, formula traceability) for Logic/Integration stories.
  • Evaluate manual evidence quality (criterion linkage, sign-offs, artefact completeness, freshness) for Visual/UI stories.
  • Build a structured review report with verdicts and actionable guidance.

Quick Start

Run the review on a single story path to audit tests and evidence.

Frequently Asked Questions about test-evidence-review

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

FAQPage Schema
How do I evaluate test coverage and assertion quality before QA sign-off?

You can evaluate test coverage before QA sign-off by reviewing test files and evidence documents to check assertion presence, edge-case handling, naming conventions, and verification sign-offs, yielding ADEQUATE, INCOMPLETE, or MISSING verdicts.

What is the best way to automate quality checks for test evidence across a sprint?

Automating quality checks for test evidence across a sprint requires parsing argument scopes to identify stories, locating unit and integration test artifacts, and evaluating assertion coverage to produce structured review reports with actionable guidance.

How do I review manual evidence quality for Visual and UI stories?

To review manual evidence quality for Visual and UI stories, evaluate criterion linkage, sign-offs, artefact completeness, and freshness within the evidence documents to ensure thorough verification and generate accurate review verdicts.

Does test evidence review work for single story, sprint, and system scopes?

Test evidence review supports single story, sprint, and system scopes by parsing argument scopes to identify stories and locating matching test and evidence files across unit, integration, and QA artifacts for comprehensive quality evaluation.

Why does my test coverage review return an INCOMPLETE verdict?

Your test coverage review returns an INCOMPLETE verdict when test files or manual evidence documents lack adequate assertion presence, edge-case coverage, naming quality, or verification sign-offs required for a complete QA evaluation.