test-case-reviewer-plus · diff
git:20260325.c371d73 to git:20260803.f52f41e
30 added, 20 removed. Audit A to A.
---
name: test-case-reviewer-plus
- description: Review test cases using requirement, strategy, and supporting documents, then output structured findings.
+ description: 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.
---
# 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.
- ## Output Format Options
+ ## Workflow
- Markdown by default unless the request explicitly asks for another format.
+ 1. Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
+ 2. Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
+ 3. If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
+ 4. Default to Markdown; switch formats only when the user asks.
- ## How to Use
+ ## Core Constraints
- 1. Open `prompts/test-case-reviewer-plus.md` and use it as the main prompt.
- 2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
- 3. If the input is incomplete, return a usable first version and mark missing information and assumptions.
+ - 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.
- ## Reference Files
+ ## Progressive Disclosure
- - `prompts/test-case-reviewer-plus.md`: main prompt for this skill.
- - `examples/`: sample inputs or outputs.
- - `scripts/`: helper scripts or converters for this skill.
+ - 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.
- ## Common Pitfalls
+ ## Pre-delivery Checklist
- - Do not use it with vague scope and no context.
- - Do not treat every area as equally important.
- - Do not skip assumptions and missing information.
+ - [ ] 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
- ## Best Practices
+ ## Common Pitfalls
- - Start from the prompt file, then add only the context that matters.
- - Keep the output risk-driven and executable.
- - If the request is incomplete, return a usable first version and mark gaps.
+ - 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.