code▌

Refactor code while preserving behavior, improving clarity, and reducing complexity. \n \n Covers five core refactoring patterns: Extract Method, DRY principle removal, conditional-to-polymorphism conversion, parameter object introduction, and SOLID principle application \n Includes behavior validation workflow with pre-refactoring analysis, post-refactoring testing (unit, type, lint, snapshot), and change documentation \n Provides refactoring checklist covering function length, parameter count,

Comprehensive software craftsmanship guide based on Robert C. Martin's "Clean Code: A Handbook of Agile Software Craftsmanship", updated with modern corrections where the original 2008 advice has been superseded. Contains 48 rules across 10 categories, prioritized by impact to guide code reviews, refactoring decisions, and new development. Examples are primarily in Java but principles are language-agnostic.

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

Simple, pragmatic, opinionated. Only what matters for writing production-grade Rust code.

Expert code review of current git changes with a senior engineer lens. \n \n Detects SOLID violations (SRP, OCP, LSP, ISP, DIP), architecture smells, and proposes incremental refactors with clear rationale \n Scans for security risks including injection, XSS, AuthZ gaps, race conditions, and unsafe deserialization with exploitability assessment \n Identifies removal candidates and unused code with safe deletion vs. deferred plans and concrete follow-up checkpoints \n Flags code quality issues: e

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

Perform comprehensive code reviews of GitLab merge requests, providing actionable feedback on code quality, security, performance, and best practices.

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

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