test-evidence-review

Featured

Quality review of test files and manual evidence documents. Goes beyond existence checks — evaluates assertion coverage, edge case handling, naming conventions, and evidence completeness. Produces ADEQUATE/INCOMPLETE/MISSING verdict per story. Run before QA sign-off or on demand.

Code & Development 40,030 stars 5224 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 97/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Test Evidence Review `/smoke-check` verifies that test files **exist** and **pass**. This skill goes further — it reviews the **quality** of those tests and evidence documents. A test file that exists and passes may still leave critical behaviour uncovered. A manual evidence doc that exists may lack the sign-offs required for closure. **Output:** Summary report (in conversation) + optional `production/qa/evidence-review-[date].md` **When to run:** - Before QA hand-off sign-off (`/team-qa` Phase 5) - On any story where test quality is in question - As part of milestone review for Logic and Integration story quality audit --- ## 1. Parse Arguments **Modes:** - `/test-evidence-review [story-path]` — review a single story's evidence - `/test-evidence-review sprint` — review all stories in the current sprint - `/test-evidence-review [system-name]` — review all stories in an epic/system - No argument — ask which scope: "Single story", "Current sprint", "A system" --- ## 2. Load Stories in Scope Based on the argument: **Single story**: Read the story file directly. Extract: Story Type, Test Evidence section, story slug, system name. **Sprint**: Read the most recently modified file in `production/sprints/`. Extract the list of story file paths from the sprint plan. Read each story file. **System**: Glob `production/epics/[system-name]/story-*.md`. Read each. For each story, collect: - `Type:` field (Logic / Integration / Visual/Feel / UI / Config/Data) - `## Test Evide...

Details

Author
Donchitos
Repository
Donchitos/Claude-Code-Game-Studios
Created
9 months ago
Last Updated
1 weeks ago
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Featured

test-evidence-review

Quality review of test files and manual evidence documents. Goes beyond existence checks — evaluates assertion coverage, edge case handling, naming conventions, and evidence completeness. Produces ADEQUATE/INCOMPLETE/MISSING verdict per story. Run before QA sign-off or on demand.

126 Updated 5 days ago
striderZA
Testing & QA Listed

test-evidence

Use when asked "do our load tests match our latency target?", "will the load test catch a slow release?", "do we have mutation testing?", "what is our mutation score?", or when quality-review flags the load or mutation lens. Checks that a k6, Artillery or Locust load test asserts the p95 latency and reaches the request rate in the contract's targets (QA-L1–L5), and that a mutation tool is configured, run by CI and backed by a current score in the repository (QA-M1–M4). Read-only; never runs a load test or a mutation tool.

0 Updated today
lloydbrian
Code & Development Listed

review-evidence

Use when a delivery run dispatches a verification-stretch evidence-judging action: test evidence (test_evidence_review, qa-engineer), security evidence (security_evidence_review, security-reviewer), runtime evidence (runtime_evidence_review, devops-ops), or documentation evidence (documentation_evidence_review, documentation-steward). One shared procedure — judge recorded evidence against what it claims, prove existing work without expanding scope, record residual findings explicitly even when empty — parameterized by the action id passed as the first skill argument and the persona dispatched. Replaces the retired test-evidence-review, security-evidence-review, runtime-evidence-review, and documentation-evidence-review skills.

0 Updated 3 months ago
BhangeeF16