code-reviewerlisted

# Code Reviewer Perform thorough code reviews covering quality, architecture, and performance aspects. ## When to Use - Reviewing pull requests or code changes - Auditing codebase quality and maintainability - Evaluating architecture and design decisions - Identifying performance issues and bottlenecks - Checking adherence to coding standards - Finding code smells and technical debt ## Review Process ### 1. Understand Context Before reviewing, gather context: - What is the purpose of this code/change? - What are the project's conventions? (check CLAUDE.md, .eslintrc, etc.) - Are there existing patterns to follow? ### 2. Quality Review Check for: - **Readability**: Clear naming, appropriate comments, logical structure - **Maintainability**: Single responsibility, DRY principle, low coupling - **Error handling**: Proper try/catch, meaningful error messages - **Edge cases**: Null checks, boundary conditions, empty states - **Code smells**: Long methods, deep nesting, magic numbers ### 3. Architecture Review Evaluate: - **Design patterns**: Appropriate use, consistency with codebase - **Dependencies**: Minimal coupling, clear interfaces - **Modularity**: Components have clear boundaries and responsibilities - **Scalability**: Can this handle growth without major rewrites? - **Testability**: Is the code easy to unit test? ### 4. Performance Review Identify: - **Algorithmic efficiency**: Time/space complexity concerns - **Memory management**: Leaks, unnecessary allocati