skills.rest
Euraika-Labs
Euraika-LabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

test-evidence-review

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

14|1|Updated Apr 12, 2026
Search Tags:#qa#sign-off#edge-cases#naming#evidence-quality#test-review#assertion-coverage
One-click install
npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill test-evidence-review-euraika-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/test-evidence-review
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill test-evidence-review-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures that test files and manual evidence documents are not only present but also meet quality standards such as adequate assertion coverage, edge‑case handling, proper naming, and complete sign‑offs, preventing gaps before QA sign‑off or release.

Core Features & Use Cases

  • Assertion analysis: Counts and evaluates assertions in unit and integration tests.
  • Edge‑case detection: Checks tests for coverage of boundary conditions and special inputs.
  • Naming and formula traceability: Validates descriptive test names and links to formulas.
  • Evidence completeness: Verifies that manual evidence documents reference all acceptance criteria and contain required sign‑offs.
  • Scope flexibility: Can review a single story, an entire sprint, or all stories within a system.

Quick Start

Run test-evidence-review sprint to evaluate the quality of all tests and evidence for 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 review test evidence for QA sign-off?▼

To review test evidence for QA sign-off, evaluate assertion coverage, edge-case handling, naming conventions, and formula traceability to produce ADEQUATE, INCOMPLETE, or MISSING verdicts for release readiness.

What does assertion coverage analysis check in unit and integration tests?▼

Assertion coverage analysis counts and evaluates assertions in unit and integration tests to ensure boundary conditions and special inputs are handled, validating descriptive test names and formula traceability.

Can I check edge-case handling and naming conventions for an entire sprint?▼

Yes, you can check edge-case handling and naming conventions for a single story, an entire sprint, or all stories within a system during milestone audits by adjusting the review scope.

What is the best way to verify manual evidence completeness before release?▼

The best way to verify manual evidence completeness is to confirm that documents reference all acceptance criteria and contain required sign-offs, preventing gaps before QA sign-off or release.

Why does test review return an INCOMPLETE verdict during milestone audits?▼

Test review returns an INCOMPLETE verdict during milestone audits when test files or evidence documents lack adequate assertion coverage, proper naming conventions, or complete sign-offs for acceptance criteria.

Related Skills

Explore More Software Engineering Skills→
raiichraiich
1

doc-reviewer

Review Markdown files for naming, conciseness, consistency, and completeness.

Community
Basic
jamesrochabrunjamesrochabrun
194

qa-test-planner

Generate QA test plans, manual cases, regression suites, and bug reports.

Community
Advanced
ajstack22ajstack22

atlas-agent-peer-reviewer

Review pull requests and patches with evidence-based verdicts.

Community
Intermediate
lushly-devlushly-dev
4

enforce-standards

Enforce coding conventions for Python, TypeScript, HTML, and CSS.

Official
Intermediate