coding-standards
Code-Standards. Use when reviewing code style or formatting.
Code-Standards. Use when reviewing code style or formatting.
Regel 03: Codierungsstandards. Use when reviewing code style or formatting.
Standards de Code. Use when reviewing code style or formatting.
Regra 03: Padrรตes de Codificaรงรฃo. Use when reviewing code style or formatting.
Rule 03: Coding Standards. Use when reviewing code style or formatting.
Coding-Standards fรผr React. Use when reviewing code style or formatting.
Estรกndares de Cรณdigo. Use when reviewing code style or formatting.
Regla 03: Estรกndares de Codificaciรณn. Use when reviewing code style or formatting.
่ฟ่กๅ จ้ข็ไปฃ็ ๅฎกๆฅ๏ผๆถต็ๅฎๅ จใๆง่ฝไธๅฏ็ปดๆคๆงๅๆใ้็จไบ็จๆท่ฆๆฑๅฎกๆฅไปฃ็ ใๆๆฅ็ผบ้ทๆๅฎก่ฎกไปฃ็ ๅบ็ๅบๆฏใ
Expert code review for quality, security, and maintainability. Use after writing or modifying code, or when user asks for review.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Systematic code review skill checking documentation quality and promoting code reuse
Use when writing TypeScript code, reviewing TS implementations, or making decisions about type declarations, function styles, or naming conventions - comprehensive house style covering type vs interface rules, function declarations, FCIS integration, immutability patterns, and type safety enforcement
Use when invalid data causes failures deep in execution - validates at every layer data passes through to make bugs structurally impossible rather than temporarily fixed
Use when committing code changes with proper conventional commit format and verification
Comprehensive code review methodology with severity classification and confidence thresholds
Tactical code cleanup focusing on type strictness, single responsibility, fail-fast patterns, and DRY. Detects sloppy code, workarounds, silent failures, god classes, and duplication. Use for quick code quality checks before committing or during code review.
Standards for self-documenting code and minimal comments. Use when auditing inline documentation or deciding when comments add value vs clutter.
Use when formatting JavaScript/TypeScript code with Biome's fast formatter including patterns, options, and code style management.
Use during verification phase when conducting thorough code reviews and providing constructive feedback based on universal software quality principles.
Use when creating custom Credo checks for project-specific code quality rules and standards in Elixir.
Use when pylint configuration including pylintrc, message control, plugins, and scoring system.