skills.rest
CarlosQ96
CarlosQ96COMMUNITY
Explore all skills by this author →
GitHub

test-evidence-review

Review test evidence and produce ADEQUATE, INCOMPLETE, or MISSING verdicts per story.

Updated Apr 9, 2026
Search Tags:#edge-cases#evidence-management#qa-review#test-evidence#assertion-coverage#sign-offs
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill test-evidence-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/test-evidence-review
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill test-evidence-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams evaluate test quality and evidence completeness beyond mere existence checks, ensuring assertion coverage, edge-case handling, naming quality, and sign-offs to yield a reliable verdict per story.

Core Features & Use Cases

  • Reviews assertion coverage across unit/integration tests and manual evidence
  • Judges edge-case handling, naming quality, and sign-off completeness
  • Produces verdict per story: ADEQUATE / INCOMPLETE / MISSING; supports QA handoffs

Quick Start

Run the /test-evidence-review command on a story or sprint to generate a verdict and actionable improvements.

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 evidence quality for sprint stories?▼

Evaluating test evidence quality requires reviewing assertion coverage, edge-case handling, naming quality, and sign-offs to yield a reliable verdict of ADEQUATE, INCOMPLETE, or MISSING per story.

What is test evidence review in QA?▼

Test evidence review is assessing assertion coverage across unit, integration, and manual tests to verify logic, integration, visual feel, UI, and config/data stories within a sprint.

How do I check assertion coverage and edge-case handling for user stories?▼

Check assertion coverage and edge-case handling by applying a QA-grade review to the test evidence of each story, verifying that all critical paths and boundaries are explicitly asserted.

Can I generate QA sign-offs and verdicts for incomplete test evidence?▼

Yes, evaluating test evidence produces a verdict per story—ADEQUATE, INCOMPLETE, or MISSING—by judging sign-off completeness and edge-case handling to support reliable QA handoffs.

What's the best way to review test evidence across logic and integration stories?▼

The best way to review test evidence is to apply a consistent evaluation across logic, integration, visual feel, UI, and config/data stories, summarizing quality and producing actionable improvements.

Related Skills

Explore More Software Engineering Skills→
kay6198835kay6198835

test-evidence-review

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

Community
Advanced
einja-inceinja-inc
1

task-qa

Execute mandatory tests and record failure classifications for QA evidence.

Official
Advanced
ajstack22ajstack22

atlas-agent-peer-reviewer

Review pull requests and patches with evidence-based verdicts.

Community
Intermediate
cenconq25cenconq25
39

test-evidence-review

Audit per-story test coverage and documentation to identify evidence gaps.

Community
Advanced