test-evidence-review

Audit test evidence quality and story readiness across sprints.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/rakhnianskii9/God-Godot --skill test-evidence-review-rakhnianskii9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/test-evidence-review
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill test-evidence-review-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the evaluation of test evidence quality and story readiness by auditing assertions, edge cases, naming, and sign-offs.

Core Features & Use Cases

  • Review test files for assertion coverage, edge cases, and naming quality to ensure meaningful test cases.
  • Verify manual evidence documents for required sign-offs and linkage to acceptance criteria.
  • Generate a concise verdict per story (ADEQUATE / INCOMPLETE / MISSING) and compile a sprint-level summary for QA and planning.
  • Use Case: Before QA hand-off, run a comprehensive audit across a set of stories to confirm test quality and evidence completeness.

Quick Start

Run /test-evidence-review sprint to audit all stories in the current sprint.

Frequently Asked Questions about test-evidence-review

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

FAQPage Schema
How do I automate test evidence review for story sign-off before QA hand-off?

Automate test evidence review by auditing assertion coverage, edge cases, naming quality, and sign-offs. The tool parses story files and evidence documents to generate a concise ADEQUATE, INCOMPLETE, or MISSING verdict per story.

Can I audit test quality and evidence completeness for all stories in a sprint?

Yes, you can audit all stories in a sprint. Running a sprint-level command evaluates automated tests and manual evidence across the entire sprint, compiling a summary verdict for QA planning and hand-off readiness.

What is story readiness verification and how does it evaluate test files?

Story readiness verification evaluates test files by auditing assertions, checking edge case coverage, and reviewing naming conventions. It ensures automated tests and manual evidence map correctly to acceptance criteria and required sign-offs.

Does the test evidence audit check both automated unit tests and manual evidence documents?

Yes, the test evidence audit enforces criteria for both automated tests and manual evidence. It verifies required sign-offs and linkage to acceptance criteria while reviewing test files for meaningful assertion coverage.

How do I evaluate test evidence quality across multiple epics and systems?

Evaluate test evidence across systems by running a system-level audit. The review parses story files and evidence documents within the specified system boundaries to verify test quality, edge cases, and sign-off completeness.

What are the limitations of automating story verification for test evidence?

Automating story verification requires parseable story files and linked evidence documents to function. It cannot evaluate test quality or sign-off completeness if the evidence locations or test file mappings are missing or improperly formatted.