Agent skill · software engineering · aiskillstore
code-reviewer
Use when asked to review MERN stack code - comprehensive code reviewer that checks project health, security, maintainability, performance, testing, and architecture. Combines general code quality analysis with MERN-specific expertise.
Why this skill is useful
Adds a comprehensive checklist and workflow for reviewing MERN stack code that includes specific project health checks and security practices not commonly found in generic reviews.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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: 1. Build status: Run tsc --noEmit or check for compilation errors 2. Project docs: Read README, any STATUS/BUGS/TODO files - look for deployment blockers 3. Test health: Do tests exist? Check package.json scripts, look for test directories 4. File sizes: find src -name ".ts" -o -name ".tsx" xargs wc -l sort -n tail -20 5. Dependencies: Check for npm audit issues, unusual deps (Angular in React?) Stop here if: Build is broken, docs say "DO NOT DEPLOY", or critical blockers found. Report immediately. Phase 1: Scope Detection 1. Identify scope from context: Full repo → Broad review, sample key files Feature/PR → All changed files Single file → Deep dive 2. Detect layers: React? Express? MongoDB? Node.js? 3. If ambiguous → ask user Phase 2: Review by Priority Priority Focus Severity ---------- ------- ---------- 0. Blockers Build failures, "DO NOT DEPLOY", broken deploys STOP 1. Security Injection, auth, secrets, XSS Critical 2. Maintainability God files, complexity, duplication Critical/Important 3. Performance N+1, missing indexes, re-renders Important 4. Testing No tests, low coverage, flaky tests Important 5. Best Practices Error handling, async patterns Suggestion 6. Architecture API design, state management Suggestion Load reference files ON-DEMAND when you hit MERN-specific edge cases. Phase 3: Report Use the output format below. Offer to fix starting with Critical. Output Format Checklists Minimum required checks. Report other issues you find during review. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/code-reviewer