test-evidence-review

Name: test-evidence-review
Availability: InStock
Author: nguyennd93

Evaluate test file assertion coverage and manual evidence criteria completion.

Updated Jul 4, 2026

Search Tags:#code analysis #automated testing #software validation #QA automation #test quality review

Ready to run

npx skills add https://github.com/nguyennd93/game_server_studio --skill test-evidence-review-nguyennd93

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/nguyennd93/game_server_studio/tree/main/.claude/skills/test-evidence-review
Command: npx skills add https://github.com/nguyennd93/game_server_studio --skill test-evidence-review-nguyennd93

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the quality review of test files and manual evidence documents, providing a verdict on adequacy, incompleteness, or missing elements.

Core Features & Use Cases

Automated Test Quality Review: Evaluates assertion coverage, edge case handling, naming conventions, and evidence completeness for test files.
Manual Evidence Quality Review: Checks for criterion linkage, sign-off completeness, screenshot/artifact completeness, and date coverage for evidence documents.
Use Case: Before QA sign-off or on demand, use this Skill to ensure test files and evidence meet required standards.

Quick Start

Run /test-evidence-review /path/to/story to review the test files and evidence for a specific story.

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 quality reviews for test files and manual evidence documents?▼

To automate test file and evidence review, run the Skill against a project directory path to evaluate assertion coverage, naming conventions, and criteria completion, yielding a verdict on document adequacy.

What does automated test assertion coverage evaluation check for in a project?▼

Automated test assertion coverage evaluation inspects test files for edge case handling, naming conventions, and assertion completeness to determine if the tests meet required quality standards before QA sign-off.

How do I review manual evidence criteria completion for a specific sprint?▼

To review manual evidence criteria completion for a sprint, target the specific directory path to check for criterion linkage, sign-off completeness, screenshot artifacts, and date coverage.

Can I use this test quality review on individual stories within a larger system?▼

Yes, test quality review operates on individual stories, sprints, or systems within a project directory, allowing you to isolate and validate evidence and test files for specific project scopes.

What is the best way to check for missing elements in manual evidence documents before QA sign-off?▼

The best way to check for missing elements in evidence documents is to run an automated review that validates criterion linkage, sign-off completeness, and artifact presence, providing a clear verdict on document incompleteness.

Why does software validation report incomplete evidence for my test files?▼

Software validation reports incomplete evidence when test files lack sufficient assertion coverage, proper naming conventions, or when manual evidence documents are missing required screenshots, sign-offs, or criterion linkage.