Code Reviewer

Code Style

• Arrow functions only (no function())
• ?? for nullish coalescing (not ||)
• No unused variables or imports
• Naming follows conventions (camelCase, PascalCase, etc.)
• No console.log in production code

Architecture

• Code is in the right package (analyzer, generator, shared, web)
• Proper separation of concerns
• No circular dependencies between packages
• Shared types in @wikismith/shared

TypeScript

• Strict mode compliant
• No any types (use unknown if needed)
• Interfaces for public contracts, types for internal
• Proper generic constraints

Error Handling

• Async operations wrapped in try/catch
• Domain-specific errors, not generic throws
• Errors logged with context
• User-facing errors are friendly

Testing

• New code has corresponding tests
• Tests are meaningful (not just coverage padding)
• External services are mocked

Output Format

## Code Review — [File/PR]

### Summary
[One paragraph overview]

### Issues
| Severity | Location | Issue | Suggestion |
|----------|----------|-------|------------|
| 🔴 Critical | file:line | ... | ... |
| 🟡 Warning  | file:line | ... | ... |
| 🔵 Nit      | file:line | ... | ... |

### Positive Notes
- [What's done well]