home/categories/code-quality
category focus

Code Quality

Linters, formatters, and static analysis.

2681 स्किल्सall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
70

coding-standards

Code-Standards. Use when reviewing code style or formatting.

TheBeardedBearSAS
TheBeardedBearSAS
testing-security
open
code-quality
70

coding-standards

Regel 03: Codierungsstandards. Use when reviewing code style or formatting.

TheBeardedBearSAS
TheBeardedBearSAS
testing-security
open
code-quality
70

coding-standards

Standards de Code. Use when reviewing code style or formatting.

TheBeardedBearSAS
TheBeardedBearSAS
testing-security
open
code-quality
70

coding-standards

Regra 03: Padrões de Codificação. Use when reviewing code style or formatting.

TheBeardedBearSAS
TheBeardedBearSAS
testing-security
open
code-quality
70

coding-standards

Rule 03: Coding Standards. Use when reviewing code style or formatting.

TheBeardedBearSAS
TheBeardedBearSAS
testing-security
open
code-quality
70

test-sync

Detect orphaned tests, obsolete assertions, and test-code misalignment. Use for test suite maintenance, cleanup, and traceability validation. Use when relevant to the task.

jmagly
jmagly
testing-security
open
code-quality
70

coding-standards

Coding-Standards für React. Use when reviewing code style or formatting.

TheBeardedBearSAS
TheBeardedBearSAS
testing-security
open
code-quality
70

coding-standards

Estándares de Código. Use when reviewing code style or formatting.

TheBeardedBearSAS
TheBeardedBearSAS
testing-security
open
code-quality
70

coding-standards

Regla 03: Estándares de Codificación. Use when reviewing code style or formatting.

TheBeardedBearSAS
TheBeardedBearSAS
testing-security
open
code-quality
68

code-review

进行全面的代码审查,涵盖安全、性能与可维护性分析。适用于用户要求审查代码、排查缺陷或审计代码库的场景。

linkxzhou
linkxzhou
testing-security
open
code-quality
66

code-review

Expert code review for quality, security, and maintainability. Use after writing or modifying code, or when user asks for review.

htlin222
htlin222
testing-security
open
code-quality
65

critical-code-reviewer

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.

posit-dev
posit-dev
testing-security
open
code-quality
65

review-standard

Systematic code review skill checking documentation quality and promoting code reuse

Synthesys-Lab
Synthesys-Lab
testing-security
open
code-quality
64

howto-code-in-typescript

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

ed3dai
ed3dai
testing-security
open
code-quality
64

defense-in-depth

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

ed3dai
ed3dai
testing-security
open
code-quality
62

knownscommit

Use when committing code changes with proper conventional commit format and verification

knowns-dev
knowns-dev
testing-security
open
code-quality
61

code-review

Comprehensive code review methodology with severity classification and confidence thresholds

kdcokenny
kdcokenny
testing-security
open
code-quality
61

unslopify

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.

shanev
shanev
testing-security
open
code-quality
60

documenting-code-comments

Standards for self-documenting code and minimal comments. Use when auditing inline documentation or deciding when comments add value vs clutter.

rileyhilliard
rileyhilliard
testing-security
open
code-quality
59

biome-formatting

Use when formatting JavaScript/TypeScript code with Biome's fast formatter including patterns, options, and code style management.

TheBushidoCollective
TheBushidoCollective
testing-security
open
code-quality
59

code-reviewer

Use during verification phase when conducting thorough code reviews and providing constructive feedback based on universal software quality principles.

TheBushidoCollective
TheBushidoCollective
testing-security
open
code-quality
59

kissdryer

Validate code for KISS and DRY principles. Use when asked to check for simplification opportunities, reduce duplication, review code complexity, or ensure maintainability. Works on whole codebase or specific changes (branch, PR, uncommitted).

vasylenko
vasylenko
testing-security
open
code-quality
59

credo-custom-checks

Use when creating custom Credo checks for project-specific code quality rules and standards in Elixir.

TheBushidoCollective
TheBushidoCollective
testing-security
open
code-quality
59

pylint-configuration

Use when pylint configuration including pylintrc, message control, plugins, and scoring system.

TheBushidoCollective
TheBushidoCollective
testing-security
open
Previous
Page 51 / 112
Next