code▌

Dispatch code review subagents with focused context to catch issues before they compound. \n \n Integrates with subagent-driven development workflows, triggering review after each task or before merging to main \n Provides code-reviewer subagent with precise git SHAs, implementation details, and requirements, keeping reviewer focused on work product rather than session history \n Categorizes feedback into Critical (fix immediately), Important (fix before proceeding), and Minor (note for later) s

Comprehensive, library-agnostic checklist for reviewing Flutter/Dart applications. These principles apply regardless of which state management solution, routing library, or DI framework is used.

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans.

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 SQLAlchemy and Alembic code.

Code Components: Custom React components added to canvas. Support addPropertyControls.

Expert code review of git changes with focus on SOLID violations, security risks, and actionable improvements. \n \n Analyzes current git diff for SOLID principle violations, architecture smells, and removal candidates using structured checklists \n Scans for security risks including injection, authentication gaps, race conditions, and unsafe deserialization with exploitability assessment \n Flags code quality issues: error handling gaps, N+1 queries, boundary condition bugs, and performance hot

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.

Production-grade code standards emphasizing correctness, crash-safety, and Rust idioms over convenience. \n \n Prioritizes data integrity: crash on invalid state rather than corrupt data; assert invariants aggressively; handle all errors explicitly \n Rust-specific patterns: make illegal states unrepresentable, use exhaustive pattern matching and enums over strings, minimize allocations \n Comments document why , not what ; avoid temporal markers, AI conversation references, and code-repeating e

Generate beautiful code snippet images using ray.so and save them locally.