• 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.

• Identify quality defects in test cases with structured scoring and revision priority queue.
• Output actionable revision items by impact priority.
• Improve case clarity, coverage balance, and maintainability.

1. Check requirement traceability and scenario completeness.
2. Review atomicity, readability, and reproducibility.
3. Detect overlap, obsolete logic, and inconsistent expectations.
4. Assess risk coverage for critical/edge/negative paths.
5. Mark findings with severity and fix recommendation.
6. Produce review summary and re-review gate.

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

Input:

• "Please review quickly"

Output (problem):

• Only spelling edits, no coverage or risk analysis
• No prioritized fix list

• 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.