Code Review & Quality for Claude Code

Optimize TypeORM entities for performance, query efficiency, migration safety, and relationship design — analyze decorators, indexes, eager loading, and connection pooling.

Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships

The most comprehensive Claude Code plugin — 14+ agents, 56+ skills, 33+ commands, and production-ready hooks for TDD, security scanning, code review, and continuous learning

Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "avoid technical debt", "code ownership", or "how do I become a better developer". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, do

Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", "decompose conditional", or "clean up this messy code". Also trigger when cleaning up legacy code, preparing code for new features by restructuring, or identifying which transformation fits a specific code smell. Covers smell-driven refactoring, safe tran

Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", "pass-through method", "this code is over-engineered", or "simplify this design". Also trigger when reviewing an interface for simplicity, evaluating whether an abstraction is pulling its weight, deciding whether a comment is worth writing,

Safely change and test untested codebases using Feathers'' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it

End-to-end GitHub repository maintenance for open-source projects. Use when asked to triage issues, review PRs, analyze contributor activity, generate maintenance reports, or maintain a repository. Triggers include "triage", "maintain", "review PRs", "analyze issues", "repo maintenance", "what needs attention", "open source maintenance", or any request to understand and act on GitHub issues/PRs. Supports human-in-the-loop workflows with persistent memory across sessions.

Audit and improve Jetpack Compose runtime performance from code review and architecture. Use when asked to diagnose slow rendering, janky scrolling, excessive recompositions, or performance issues in Compose UI.

Kotlin Coroutines review and remediation for Android. Use when asked to review concurrency usage, fix coroutine-related bugs, improve thread safety, or resolve lifecycle issues in Kotlin/Android code.

Deep codebase exploration to gather context for prompt optimization

You are a coding agent from the Hello World extension.

Run Rigor Analyze on this repository using the current compatible slug.

CLAUDE.md compliance scorecard — tallies which rules Claude actually follows vs ignores as you edit, and flags chronically-ignored rules to promote into a deterministic hook.

A personal flight recorder for Claude Code quality — records your own per-session failure rate, edit churn, and tokens/task by model version, and flags real shifts when a model changes.

Codebase search and context retrieval using hybrid semantic/lexical search with neural reranking

Analyze the specified component and provide recommendations

Show a summary of potential naming clashes detected in the codebase with analysis.

Regenerate Project Manifest

Regenerate Repository Map

Resolve Naming Clashes

Semantic code search using mgrep for efficient codebase exploration. This skill should be used when searching or exploring codebases with more than 30 non-gitignored files and/or nested directory structures. It provides natural language semantic search that complements traditional grep/ripgrep for finding features, understanding intent, and exploring unfamiliar code.

Evaluates code against Apple's App Store Review Guidelines for iOS, macOS, tvOS, watchOS, and visionOS apps

Cross-agent review workflow: Claude implements, Codex reviews

Pre-publish ML/systems claim check for substacker drafts. Extracts atomic technical claims from prose, classifies each as simplified-correct / simplified-boundary / wrong / contested / overclaim, cross-references primary sources (arXiv, RFC, textbooks — never blog posts), flags boundary-breaks as teaching opportunities to fold into the post. Never rewrites the draft. 48h research cap per draft. Use after Editor approves voice and before the writer publishes a post that makes technical claims (es

Enforce completion of all 7 production safety gates with evidence before any deployment. Blocks rationalized shortcuts under time, authority, sunk-cost, or exhaustion pressure. Gates: tests, security scan, breaking changes, config validation, staging verification, rollback plan, code review.

Autonomous Claude + Codex review loop. Plan a feature with adversarial pushback, or audit code, all in one window.

Ship software systematically: project lifecycle, TDD, parallel agents, code review, security auditing, and infrastructure validation

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

Review and redline a contract — risk and missing clauses

Frontend reconnaissance — map the component tree, routing, state management, build config, and assess quality. Use when asked to "understand this frontend", "frontend assessment", or "what's the UI built with".

Audit ranking quality — metric trends, failure modes, dataset coverage, reranker performance.

Backend reconnaissance — map all routes, middleware, models, dependencies, auth, and assess code quality for project takeover. Use when asked to "understand this backend", "map the API", or "assess code quality".

API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".

Firmware reconnaissance for takeover — inventory the MCU, peripherals, RTOS, protocols, OTA, power management, and assess code quality with risk flags. Use when asked to "understand this firmware", "device inventory", or "embedded assessment".

Auto-dev platform for agent-majority software teams. Five skills (auto-dev, auto-env, auto-req, auto-test, auto-triage), four roles (dev-agent, req-agent, user-agent, triage-agent), and cross-skill contracts. Humans supply requirements and intervene at key decision points; agents handle everything else.

Professional GitHub PR reviews with pending reviews, code suggestions, and user approval workflow