code▌

Structured code review framework covering quality, security, performance, and testing standards. \n \n Provides eight-step review methodology: context understanding, high-level architecture assessment, detailed code inspection, security audit, performance analysis, testing validation, documentation check, and constructive feedback delivery \n Covers SOLID principles, naming conventions, error handling, input validation, authentication/authorization, SQL injection and XSS prevention, and resource

Code simplification and refactoring focused on clarity, consistency, and maintainability. \n \n Applies project-specific best practices from CLAUDE.md, including ES modules, explicit type annotations, and proper React patterns \n Eliminates unnecessary complexity through reduced nesting, clearer naming, and removal of redundant abstractions \n Avoids nested ternaries and overly compact solutions in favor of explicit, readable code structures \n Preserves all original functionality and behavior w

Structured patterns and techniques for improving code quality through safe, behavior-preserving refactoring. \n \n Covers common code smells including long methods, deeply nested conditionals, primitive obsession, and feature envy with before/after examples \n Provides core refactoring techniques: extract method, replace conditional with polymorphism, introduce parameter objects, and replace magic numbers with constants \n Emphasizes safe refactoring workflow: ensure test coverage first, make sm

Behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity and clarity in coding practices.

These are idiomatic FastAPI patterns that may appear problematic but are correct:

Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.

Delivers changes incrementally to manage large features effectively.

When explaining code, always include: \n \n Start with an analogy : Compare the code to something from everyday life \n Draw a diagram : Use ASCII art to show the flow, structure, or relationships \n Walk through the code : Explain step-by-step what happens \n Highlight a gotcha : What's a common mistake or misconception? \n \n Keep explanations conversational. For complex concepts, use multiple analogies.

Systematic Go code review against community style standards and best practices. \n \n Covers 15+ review categories: formatting, documentation, error handling, naming, concurrency, interfaces, data structures, security, declarations, functions, style, logging, imports, generics, and testing \n Includes automated pre-review checks via gofmt , go vet , and golangci-lint to catch mechanical issues before manual review \n Organizes findings by severity (must-fix, should-fix, nit) using a consistent t

Simple, pragmatic, opinionated. Only what matters for writing production-grade PostgreSQL queries.