Code Review & Quality for Claude Code

Blind Comparator Agent

Evaluate expectations against an execution transcript and outputs.

Blind Comparator Agent

Blind Comparator Agent

Blind Comparator Agent

Evaluate expectations against an execution transcript and outputs.

Evaluate expectations against an execution transcript and outputs.

Evaluate expectations against an execution transcript and outputs.

Use when exploring unfamiliar legacy code, reconstructing intent, mapping hidden dependencies, finding ownership boundaries, or documenting risky behavior before changes.

Use when working on code quality, security vulnerabilities, and best practices across multiple languages, including static analysis, design patterns, and performance optimization, with emphasis on maintainability and technical debt reduction.

Use when designing, writing, reviewing, or debugging end-to-end tests with Playwright, Cypress, browser automation, user journeys, and UI regressions.

Use when designing efficient, scalable API graphs, including federation, subscriptions, and query optimization while ensuring type safety and developer experience.

Use when building, reviewing, or debugging Next.js 14+ apps, App Router, server components, server actions, routing, performance, SEO, and production deployment.

Use when building, reviewing, or debugging Node.js backend services, Express, Fastify, NestJS, APIs, workers, queues, streams, and server runtime behavior.

Use when working on modern PHP 8.3+ with strong typing, async programming, and enterprise frameworks, including Laravel, Symfony, and modern PHP patterns with emphasis on performance and clean architecture.

Use when working on modern Python 3.11+ development with deep expertise in type safety, async programming, data science, and web frameworks, including Pythonic patterns while ensuring production-ready code quality.

Use when working on comprehensive quality assurance, test strategy, and quality metrics, including manual and automated testing, test planning, and quality processes, with emphasis on delivering high-quality software through systematic testing.

Use when working on Rails 8.1 with modern conventions, including convention over configuration, Hotwire/Turbo, Action Cable, and rapid application development, with emphasis on building elegant, maintainable web applications.

Use when working on safe code transformation techniques and design pattern application, including improving code structure, reducing complexity, and enhancing maintainability while preserving behavior, with emphasis on systematic, test-driven refactoring.

Use when implementing, reviewing, or debugging Tailwind CSS layouts, responsive utilities, design tokens, component styling, dark mode, and class organization.

Use when designing test strategy, coverage plans, test pyramids, fixtures, CI gates, quality metrics, or refactoring brittle test suites.

Use when designing, reviewing, or debugging TypeScript types, strictness, generics, inference, module boundaries, tsconfig, and JavaScript-to-TypeScript migrations.

Use when designing, refactoring, or debugging Vue 3 components, Composition API patterns, props/emits, slots, composables, and component architecture.

Use when building, reviewing, or debugging Nuxt and Vue apps, SSR, routing, server routes, data fetching, modules, hydration, and deployment behavior.

Proactive methodology guidance agent. Monitors note creation and provides real-time quality advice. Suggests connections, flags quality issues, recommends MOC updates. Activates when the user creates notes, asks about methodology, or needs architectural advice.

> Perform vault maintenance: detect inconsistencies, merge duplicates, fix broken links, ensure structural integrity, and track vault health over time. Use when the user wants quality assurance or cleanup of their Obsidian vault. Triggers: "weekly review", "check the vault", "maintenance", "vault maintenance", "check consistency", "are there duplicates?", "fix the vault", "weekly cleanup", "vault health", "quick health check", "consistency report", "growth analytics", "stale content", "review se

> Perform vault maintenance: detect inconsistencies, merge duplicates, fix broken links, ensure structural integrity, and track vault health over time. Use when the user wants quality assurance or cleanup of their Obsidian vault. Triggers: "weekly review", "check the vault", "maintenance", "vault maintenance", "check consistency", "are there duplicates?", "fix the vault", "weekly cleanup", "vault health", "quick health check", "consistency report", "growth analytics", "stale content", "review se

The quality inspector that keeps your vault healthy, consistent, and trustworthy.

Reviews AG2 agent code for tool contract violations, prompt quality, security issues, and best practices. Invoke after creating or modifying AG2 agents.

QA Engineer and Security Auditor agent for code review, security auditing, testing verification, compliance checking, dead code detection, and quality gates. Use after any code changes or before releases.

Quantitative report auditor. Use PROACTIVELY whenever a Markdown report contains probability claims, EV calculations, pass-rate estimates, MC results, or backtest summaries. Catches probability stacking (1−(1−p)^N vs N×p), conditional-vs-marginal pass-rate confusion, percentage-vs-percentage-points mixups, bootstrap-with-replacement implications, EV-per-eval × N misuse, best-of-N selection bias, and sample-size red flags. Returns a structured P1/P2/P3 severity table.

Performs deep code review checking architecture compliance, code quality, security issues, and best practices adherence

The Boss of the dev team. Senior architect with 20 years of scars. Listens, synthesizes, and makes the final call at the end.

Scout and reader specialist for vault graph traversal, comms polling, file and directory listings, code spelunking, and any read-only reconnaissance task. Never builds -- returns structured findings only. Part of the operator-kit five-agent starter kit.

Developer and Software Architect agent for architecture decisions, full-stack implementation, code writing, testing, infrastructure, CI/CD, and technical documentation. Use for any coding, implementation, architecture, refactoring, or technical task.

Deeply analyzes codebase for a phase and returns structured assumptions with evidence. Spawned by discuss-phase assumptions mode.

Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.

Reviews source files for bugs, security issues, and code quality problems. Produces structured REVIEW.md with severity-classified findings. Spawned by /gsd:code-review.

Explores codebase and writes structured analysis documents. Spawned by map-codebase with a focus area (tech, arch, quality, concerns). Writes documents directly to reduce orchestrator context load.