code▌

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

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

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

Structured code review for security, performance, correctness, and maintainability across PR diffs and file changes. \n \n Audits security risks including SQL injection, XSS, CSRF, authentication flaws, and credential exposure \n Identifies performance issues like N+1 queries, memory leaks, algorithmic complexity, and resource leaks \n Checks correctness for edge cases, race conditions, error handling, and type safety gaps \n Works standalone with diffs and file paths; integrates with source con

This skill safely identifies and removes unused code across multiple programming languages. It includes comprehensive safety checks to prevent removing code that's actually needed.

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

Skill by ara.so — Daily 2026 Skills collection.

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

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

A disciplined approach to writing code that communicates intent, minimizes surprises, and welcomes change. Apply these principles when writing new code, reviewing pull requests, refactoring legacy systems, or advising on code quality improvements.