Total 30,768 skills, Code Quality has 1625 skills
Showing 12 of 1625 skills
Review a merge request or branch. Compares a branch against main/master, summarizes changes, highlights concerns, and provides actionable feedback. Use for PR reviews or before merging.
Simplify code and remove legacy/backcompat shims while preserving behavior. Use when asked to clean up or simplify code.
Always use this skill when dealing with code of any kind. Wether writing, reading, reviewing or something else. If it's code use this skill.
Use before committing code - validates Drupal coding standards, SOLID/DRY principles, security practices, and CSS standards
When dealing with python code, these guidelines must always be followed.
Review code changes for quality, correctness, and best practices. Use when asked to review a PR, review changes, or assess code quality before merge.
Write Rust code in the style of Niko Matsakis, Rust language team lead. Emphasizes deep understanding of ownership, lifetimes, and the borrow checker. Use when working with complex lifetime scenarios or designing APIs that interact with the ownership system.
TDD enforcement during implementation. Reads `tdd:` setting from CLAUDE.md. Modes - strict (human approval for escape), soft (warnings), off (disabled). Auto-invoked by /implement.
Use when writing or modifying any code. Enforces naming conventions, function design, and code clarity principles.
Removes AI-generated code slop from git diffs to maintain code quality
Creates and manages Biome GritQL custom lint rules to enforce coding patterns. Use when creating linter rules, enforcing code conventions, preventing anti-patterns, or when the user mentions Biome, GritQL, custom lint rules, or AST-based linting.
Gate 8: Zero-context implementation steps - 2-5 minute atomic subtasks with complete code, exact commands, TDD pattern. Large Track only.