Total 54,373 skills, Code Quality has 2447 skills
Showing 12 of 2447 skills
Use before committing code - validates Drupal coding standards, SOLID/DRY principles, security practices, and CSS standards
Next Friday code style rules for formatting, structure, and readability. Use when writing functions, conditionals, or organizing code.
Finds unused dependencies, files, and exports in JS/TS projects. Use when cleaning up dead code, removing stale packages from package.json, or identifying unreferenced exports.
Check code quality and formatting before committing changes
C# patterns for Unity - MonoBehaviour, async, architecture, and VR/mobile performance optimization
Expert guidance for game development with C#/Unity, Lua scripting, and best practices for scalable game architecture
Improve code performance without changing behavior. Use when code fails latency/throughput requirements. Covers profiling, caching, and algorithmic optimization.
Perform blunt, high-intensity code review in Ukrainian with a colloquial style inspired by Oleksandr Povoroznyuk. Use when users explicitly ask for a harsh/rough tone, slang-heavy feedback, or review comments "in style of Поворознюк", including optional profanity. Keep findings technically precise, actionable, and evidence-based.
This skill should be used when the user asks to "review PR and save results", "run PR review with documentation", "create PR review document", "review and document PR", "save PR review to docs", "document PR review", or mentions reviewing a PR with the intention of saving the review results. Executes comprehensive PR review using pr-review-toolkit with opus model and posts results as a PR comment.
Review code changes in a feature branch before merging. Use when asked to review a branch, review changes, check a PR, or audit code before merge. Compares the current branch against the default branch (main/master) and categorizes issues by severity (Critical, Major, Minor) with actionable solutions.
Build phase of RDD. Turns behavior scenarios into executable BDD specs, then implements via TDD (red/green/refactor). Enforces structure-vs-behavior separation, composable tests, and small reversible steps. Use after /rdd-decide when scenarios and domain model are approved.
Python code quality with ruff linter. Fast linting, rule selection, auto-fixing, and configuration. Use when checking Python code quality, enforcing standards, or finding bugs.