Use this skill to run an actionable review for changed code in this repository.
Focus on correctness, regression risk, type safety, reactivity safety, maintainability, and release readiness.
Return findings in this order:
Critical - must fix before mergeMajor - high-priority fixesMinor - improvements and consistency issuesTest Gaps - missing validation casesPass Summary - only after listing findingsIf no findings exist, explicitly state: No blocking findings.
Copy this checklist and mark progress:
Review Progress
- [ ] Step 1: Collect diff context
- [ ] Step 2: Run correctness and regression scan
- [ ] Step 3: Run Vue 3 + TS rule scan
- [ ] Step 4: Run UI and style consistency scan
- [ ] Step 5: Run testing and risk scan
- [ ] Step 6: Produce structured findings
src/views, src/components, src/composables, src/router.Check:
try/catch that hide user impactBlock merge if business flow can break under partial/empty API data.
Check against project conventions:
; avoid Options API and mixinsref for primitive/single values, reactive for structured objectsany; avoid any in composable returnsReport each issue with: violated rule + risk + suggested fix.
Check:
button, input, img) before generic divv-for where applicable, avoid broad global leakageCheck:
If tests are missing, provide a minimal test checklist.
Use this template for each issue:
- Severity: Critical | Major | Minor
- Location: `path/to/file`
- Problem: One-line behavior risk statement
- Why it matters: User/business impact
- Suggested fix: Concrete and minimal change
When no actionable issue is found, output:
No blocking findings.
Residual risks:
- [List any low-confidence assumptions]
Suggested verification:
- [Manual or automated checks to run]
Always prioritize these risk classes first:
any, unchecked cast, missing null checks)共 1 个版本