maji-reviewlisted

# maji-review — Disciplined Code Review A skill that reviews code (PR, diff, single file, or directory) and outputs structured feedback grouped by severity. No "Great work overall!" preamble. No trailing "let me know if you'd like to discuss". Just findings. --- ## When to Use Type `maji-review <target>` where target is: - A file path (`maji-review src/auth.ts`) - A diff (`maji-review` after `git diff`) - A PR URL (`maji-review https://github.com/...`) - A range (`maji-review src/`) Claude reads the target and outputs grouped feedback. --- ## Output Format ``` [Summary line: total findings + count by severity] 🔴 Critical (N findings) ────────────────────── file:line — [issue] Why: [1-sentence reason] Fix: [code snippet or pattern] 🟡 Important (N findings) ────────────────────── [same format] 🟢 Style (N findings) ────────────────────── [same format] 💡 Suggestion (N findings) ────────────────────── [same format] [Footer: 1 line — overall verdict + recommended next action] ``` --- ## Severity Categories ### 🔴 Critical (must fix before merge) - Bugs that cause incorrect behaviour - Security vulnerabilities (SQL injection, XSS, exposed secrets, etc.) - Code that crashes or throws unhandled errors - Broken types / failed compilation - Race conditions, deadlocks - Data loss / corruption risks ### 🟡 Important (should fix, may merge with follow-up) - Edge cases not handled - Missing input validation at system boundaries - Performance issues likely to bite