code▌

Comprehensive security rules for writing secure code across 15+ languages. Covers OWASP Top 10, infrastructure security, and coding best practices with 28 rule categories.

Comprehensive code simplification guide for AI agents and LLMs. Contains 47 rules across 8 categories, prioritized by impact from critical (context discovery, behavior preservation) to incremental (language idioms). Each rule includes detailed explanations, real-world examples comparing incorrect vs. correct implementations, and specific impact metrics.

Follow these guidelines when reviewing code for Sentry projects.

Generated from affaan-m/everything-claude-code on 2026-03-20

Code review framework following Sentry engineering practices for pull requests and code quality assessment. \n \n Covers six key problem areas: runtime errors, performance bottlenecks, side effects, backwards compatibility, ORM query issues, and security vulnerabilities \n Includes design assessment guidance for component interactions, architectural alignment, and requirement conflicts \n Requires appropriate test coverage across functional, integration, and end-to-end tests with verification of

Pragmatic coding standards emphasizing conciseness, single responsibility, and direct solutions. \n \n Covers five core principles: Single Responsibility, DRY, KISS, YAGNI, and the Boy Scout rule for incremental code improvement \n Provides naming conventions for variables, functions, booleans, and constants designed to self-document intent without excessive comments \n Enforces function discipline: max 20 lines, one level of abstraction, minimal arguments, and no unexpected side effects \n Incl

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

You are a code migration expert specializing in transitioning codebases between frameworks, languages, versions, and platforms. Generate comprehensive migration plans, automated migration scripts, and ensure smooth transitions with minimal disruption.

Context-driven code reviews prioritizing quality, security, testability, and maintainability. \n \n Organizes feedback into four priority levels: blockers (must fix), major issues (should fix), minor improvements, and suggestions, with clear templates and rationale for each \n Covers five core review areas: logic correctness, security risks, test coverage, performance issues, and error handling; explicitly excludes style nitpicking and formatting \n Recommends reviewing code in chunks under 400

Write-time code quality enforcement with auto-formatting, linting, and Claude-powered subprocess fixes on every file edit. \n \n Three-phase architecture: silent auto-formatting, violation collection, and tiered model routing (Haiku for style, Sonnet for complexity, Opus for types) to fix unfixable issues \n Supports Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, and Dockerfile with 20+ linters including ruff, biome, shellcheck, and hadolint \n Config protection via PreToolUse and Stop h