code-reviewer
Code Reviewer
Overview
Comprehensive code review: General intelligence + MERN specialization.
Philosophy: Check project health FIRST, then dive into code. A 6,000-line file is a problem regardless of what's in it.
Review Workflow
Phase 0: Project Health (Do This First)
Before reading any code, assess project health:
- Build status: Run
tsc --noEmitor check for compilation errors - Project docs: Read README, any STATUS/BUGS/TODO files - look for deployment blockers
- Test health: Do tests exist? Check
package.jsonscripts, look for test directories - File sizes:
find src -name "*.ts" -o -name "*.tsx" | xargs wc -l | sort -n | tail -20 - Dependencies: Check for
npm auditissues, unusual deps (Angular in React?)
More from 9tykeshav/mern-ninja-cc
backend-test-writer
Use when generating tests for backend code (Express routes, MongoDB models, Node services) - analyzes file type, detects test framework from package.json, generates comprehensive tests with setup/teardown and edge case coverage
9mongodb-query-patterns
Use when writing ANY Mongoose query (.find, .findOne, .findById, .aggregate, .populate), adding database operations to services or controllers, wiring data between services, building endpoints that read or write to MongoDB, or reviewing code that chains service calls. TRIGGER especially when about to write a new findById or pass an ID where a document could be passed instead.
8