Review recent code changes with "fresh eyes" and fix any issues found. Use before commits to catch bugs. Trigger with /quality or before git commit, bd sync, or bd close.
Review all code changes with "fresh eyes" before committing. This catches bugs that accumulate during implementation when focus is on making things work.
This is a Next.js/TypeScript/React project with Strudel live coding integration.
During implementation, we focus on "does it work?" and can miss:
git status
git diff HEAD --name-only
For each changed file, read the to understand full context. Diffs show what changed but hide the surrounding code that may be affected.
For each file, check:
Logic & Correctness
Type Safety
any types avoided where possible?Integration
Code Hygiene
console.log(, debugger, // TODO: remove)React/Next.js Specific
'use client' where needed?window/document access during server render)?next/dynamic with ssr: false)?Strudel/Audio Specific
npm run lint
npx tsc --noEmit
Fix any issues these tools report before proceeding.
When you find an issue:
Do NOT just flag issues—fix them. Only flag issues that require human judgment (design decisions, unclear requirements).
After reviewing all files, provide:
## Quality Review Summary
**Files Reviewed:** <list>
**Issues Fixed:**
- <file>: <what was fixed and why>
**Issues for Human Review:** (if any)
- <file>: <issue that requires human decision>
**Confidence:** <High/Medium/Low> - <brief explanation>