/code-review

Code Review: $ARGUMENTS

Perform a comprehensive code review.

Sections 0, 1, 2 and 5 assume a TypeScript/React stack — they are a frontend-stack example. Replace them with your language/framework equivalents (compiler check, idiomatic-usage check, perf checklist).

Target

$ARGUMENTS

If no target specified, review files changed since last commit:

git diff --name-only HEAD~1 HEAD | grep -E '\.(ts|tsx|js|jsx)$'

Review Areas

0. Compilation (run first — frontend-stack example, customize)

npx tsc --noEmit

Fix any compilation errors before proceeding with manual review.

1. TypeScript (frontend-stack example — customize)

• Check for any types
• Verify proper typing
• Look for type assertions
• Ensure npx tsc --noEmit passes

2. React (frontend-stack example — customize)

• Hooks dependencies
• Re-render optimization
• Key props on lists

3. Security

• XSS vulnerabilities
• Hardcoded secrets
• Input validation

4. Quality

• Dead code
• Error handling
• Naming conventions

5. Performance (frontend-stack example — customize)

• Waterfalls: sequential awaits → Promise.all()
• Barrel imports → direct imports
• Derived state: useEffect+setState → useMemo
• Memoization: object/array to child → useMemo/useCallback
• Non-urgent updates: heavy filters → useTransition
• Lazy loading: heavy components → dynamic()
• SSR: hydration guards for browser-only code

Output Format

🔴 Critical (must fix)

🟡 Warnings (should fix)

🟢 Good practices

📝 Suggestions