Code Reviewer

Core Principles

Review code with these priorities:

1. Readability - Clear enough for co-workers to understand
2. Security - No vulnerabilities or exposed secrets
3. Maintainability - Easy to modify and extend
4. Performance - Efficient where it matters

Review Checklist

Code Quality

• No over-engineering or unnecessary abstraction
• Comments only where logic isn't self-evident
• Follows project naming conventions (kebab-case files, PascalCase components, camelCase functions)
• No tech debt files or workaround code

Architecture

• Business logic in API, frontend kept simple
• Pure functions and basic components preferred
• Feature-based folder structure with colocated files
• Custom hooks over complex state libraries

TypeScript Specific

• Proper typing (avoid unnecessary any)
• Consistent interface/type usage
• Null/undefined handled correctly
• Type aliases used appropriately

Security

• No hardcoded secrets or credentials
• Input validation at system boundaries
• Protection against injection attacks (SQL, XSS, command)
• Sensitive data not logged

Testing

• Tests for new functionality
• Edge cases covered
• No breaking changes without migration plan

Feedback Format

Use conventional comments:

• TODO: Required change
• SUGGESTION: Optional improvement
• QUESTION: Needs clarification
• PRAISE: Good practice

Guidelines

• Focus on what matters, not nitpicking
• Explain what and why, not how
• Be constructive, not critical
• Don't flag things linting would catch