Test Case Reviewer Plus

naodeng/test-case-reviewer-plus

Use this skill when you need structured test-case review findings from requirements, strategy, and case docs; triggers include test case reviewer plus and advanced test case review.

10k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

144

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/naodeng/awesome-qa-skills --skill test-case-reviewer-plus

What comes with it

37 699 bytes besides the instruction

README.md

agents/openai.yaml

evals/cases/basic-success.yaml

evals/cases/edge-incomplete-input.yaml

evals/cases/edge-risk-priority.yaml

evals/eval.yaml

examples/analysis-sample.md

examples/plan-sample.md

examples/requirement-sample.md

examples/strategy-sample.md

examples/tech-sample.md

examples/testcase-sample.md

examples/testcase-sample.review.docx

examples/testcase-sample.review.json

examples/testcase-sample.review.md

examples/testcase-sample.review.tsv

output-templates/template-excel.tsv

output-templates/template-json.json

output-templates/template-markdown.md

output-templates/template-word.docx

prompts/test-case-reviewer-plus.md

scripts/common_formatter.py

scripts/common_parser.py

scripts/parse_excel.py

scripts/parse_html.py

scripts/parse_json.py

scripts/parse_markdown.py

scripts/parse_word.py

scripts/run_review.py

The instruction itself

7 sections, as written by the author

test-case-reviewer-plus (EN)

中文版： See the corresponding Chinese skill.

When to Use

Need a stricter review of existing test cases before test execution or release.
Need issue severity, business impact, and retest order to be explicit.

Workflow

Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
Default to Markdown; switch formats only when the user asks.

Core Constraints

Prioritize by risk / business impact — do not treat everything equally.
Separate confirmed facts from current assumptions.
Do not invent endpoints, fields, environments, or root causes the user did not provide.
Keep output executable: concrete scenarios, clear priority, clear next steps.

Progressive Disclosure

Before producing output, read and follow prompts/test-case-reviewer-plus.md (minimum coverage, output structure, quality bar).
When a ready-made template fits: use matching files under output-templates/.
When the user wants examples or alignment with existing assets: read relevant examples/.
For format conversion or helper checks: prefer existing scripts/ over reinventing.
For evaluating/regressing this skill: use evals/ with skill-up.

Pre-delivery Checklist

[ ] Followed the main prompt's output structure
[ ] Minimum coverage focus: high-severity findings, coverage gaps, missing positive scenarios, missing negative scenarios, missing boundary scenarios, traceability, step and expectation quality, business impact, ... (details in main prompt)
[ ] Covered the minimum checklist, or explained omissions
[ ] High-risk items have explicit priority
[ ] Did not invent details the user did not provide
[ ] Assumptions and gaps are marked

Common Pitfalls

Do not pretend completeness when scope/context is missing.
Do not treat every item as equally important.
Do not skip assumptions and information gaps.
Do not dump generic theory unrelated to the current toolchain.

How to use it

Copy the folder

Take naodeng/test-case-reviewer-plus from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.