Updated: 2026-03-25
test-case-reviewer
Basic Information
Full Skill Guide
When
- Existing test cases must be reviewed for quality before execution.
- Regression packs have grown and duplication risk is high.
- Team wants consistent review criteria across reviewers.
What
- Identify quality defects in test cases.
- Output actionable revision items by impact priority.
- Improve case clarity, coverage balance, and maintainability.
How
- Check requirement traceability and scenario completeness.
- Review atomicity, readability, and reproducibility.
- Detect overlap, obsolete logic, and inconsistent expectations.
- Assess risk coverage for critical/edge/negative paths.
- Mark findings with severity and fix recommendation.
- Produce review summary and re-review gate.
Reference
Positive Example (Input -> Output)
Input:
- 120 regression cases for account/profile modules
Output:
- 18 high-priority fixes (missing negative path, unstable data dependency)
- 27 merge/delete suggestions for duplicate cases
- Updated review checklist for next cycle
Negative Example (Input -> Output)
Input:
- "Please review quickly"
Output (problem):
- Only spelling edits, no coverage or risk analysis
- No prioritized fix list
Limits
- Do not rewrite all cases without issue evidence.
- Do not review in style-only mode.
- Do not ignore flaky data/environment dependency.
- Do not mark cases as passable when key assertion is missing.
- Do not close review without measurable acceptance criteria.
Usage Guide
- Install and enable
test-case-reviewerfirst (use the install commands in this page). - In your request, provide required context: scope, environment, timeline, and expected output format.
- Trigger with existing case set, for example: "Use
test-case-reviewerto review these 120 cases." - Require issue-based output: missing coverage, ambiguity, duplicates, and prioritized fixes.
- After case updates, rerun review for changed cases only.
Installation
Platform
AI Tool
Quick install (one line)
Generating command... Full script
Loading script...