skills.rest
sumilee-pcu
sumilee-pcuCOMMUNITY
Explore all skills by this author →
GitHub

test-evidence-review

Audit automated test files and manual evidence documents for coverage and sign-off completeness.

Updated Apr 15, 2026
Search Tags:#testing#qa#verification#audit#quality#evidence
One-click install
npx skills add https://github.com/sumilee-pcu/game2026 --skill test-evidence-review-sumilee-pcu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/sumilee-pcu/game2026/tree/main/.claude/skills/test-evidence-review
Command: npx skills add https://github.com/sumilee-pcu/game2026 --skill test-evidence-review-sumilee-pcu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the gap between passing tests and actual quality assurance by evaluating the depth of assertions, edge case coverage, and the completeness of manual evidence documentation.

Core Features & Use Cases

  • Automated Quality Audit: Analyzes test files for assertion density and naming conventions to ensure tests are meaningful rather than just passing.
  • Evidence Verification: Checks for required sign-offs, criterion linkage, and artifact presence in manual QA documents.
  • Use Case: Before a major release, run this to identify stories with thin test coverage or missing designer sign-offs that would otherwise block a successful deployment.

Quick Start

Run the test evidence review skill 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 check if my automated test coverage is meaningful before story closure?▼

To check if automated test coverage is meaningful, evaluate assertion density and naming conventions within test files to ensure tests are functionally valid rather than superficially passing.

What is test evidence verification in software quality assurance?▼

Test evidence verification is the process of checking manual QA documents for required sign-offs, criterion linkage, and artifact presence to validate completeness before deployment.

How do I audit sprint stories for missing designer sign-offs and thin edge case handling?▼

Audit sprint stories by analyzing edge case handling and manual evidence documents for sign-off completeness across logic, integration, and UI stories to identify blocking issues.

Can I generate a structured QA verdict report to identify blocking issues before a major release?▼

Yes, you can generate a structured verdict report by evaluating assertion coverage and evidence completeness to highlight blocking issues and advisory improvements for release readiness.

Does this test evidence review process work for UI, integration, and logic stories?▼

Yes, the test evidence review process works across UI, integration, and logic stories by analyzing assertion coverage and evidence sign-offs comprehensively across all story types.

Related Skills

Explore More Software Engineering Skills→
Euraika-LabsEuraika-Labs
14

test-evidence-review

Review test files and manual evidence documents for quality and completeness.

Official
Intermediate
imclabimclab
1

test-evidence-review

Review test files and manual evidence to produce story closure verdict reports.

Official
Intermediate
kay6198835kay6198835

test-evidence-review

Assess test evidence quality across stories, sprints, or systems.

Community
Advanced
cenconq25cenconq25
39

milestone-review

Generate a structured milestone review with verdict, completion percentages, and risk register.

Community
Advanced