← ClaudeAtlas

review-fulllisted

Run a comprehensive multi-perspective code review on recent changes. Also triggers on 'is this secure?', 'security review', 'check for vulnerabilities', 'could this be exploited?' for security-focused review. Produces: GO/NO-GO verdict + findings table (Severity | Category | File:Line | Issue | Recommendation) grouping CRITICAL/HIGH/MEDIUM/LOW across code quality (patterns, error handling, types), security (OWASP Top 10, auth gaps, hardcoded secrets), and database logic (N+1 queries, soft-delete violations, missing models).
faizkhairi/claude-code-blueprint · ★ 25 · Code & Development · score 81
Install: claude install-skill faizkhairi/claude-code-blueprint
This is a COMPREHENSIVE multi-agent code review. For quick anti-pattern scanning (seconds, not minutes), use review-diff instead. ## Step 0: Detect scope and project - If `$ARGUMENTS` is empty: review uncommitted changes (staged + unstaged via `git diff` + `git diff --cached`) - If `$ARGUMENTS` is a file path: review that file only - If `$ARGUMENTS` is a branch or range: review diff against that ref - If `$ARGUMENTS` is "security": run security-only review (skip to step 3) - Detect project type from cwd/CLAUDE.md: Framework (e.g., Nuxt/NestJS/Prisma, Next.js/React, Node/TypeScript), or Other ## Step 1: Spawn review agents in parallel Launch up to 3 agents based on what the changes touch: | Changes Touch | Agent to Spawn | Focus | |--------------|----------------|-------| | Any code | `code-reviewer` | Quality, patterns, naming, DRY, error handling, consistency | | API endpoints, auth, user input | `security-reviewer` | OWASP Top 10, injection, auth gaps, secrets, CORS | | Database queries, Prisma schema, migrations | `db-analyst` | N+1, undefined vs null, missing models, query performance | If changes are small (<50 lines), run code-reviewer only. If security argument, run security-reviewer only. ## Step 2: Code quality review (via code-reviewer agent) The agent checks: - Readability and naming conventions (matches project patterns?) - DRY -- duplicated logic that should be extracted - Error handling -- all async paths covered? Consistent error shapes? - Component/fun