Total 54,109 skills, Code Quality has 2438 skills
Showing 12 of 2438 skills
Simplify existing code without changing behavior. Focus on local complexity reduction such as flattening nesting, extracting readable helpers, removing dead code, consolidating obvious duplication, and improving names. Use when the user explicitly asks to simplify, clean up, or reduce complexity in existing code.
Runs validator checks only without AI reviews for requests such as "run validator checks", "check without reviews", or "validate before commit without AI review".
Use when writing or reviewing Kotlin type declarations to choose @JvmInline value class over data class where appropriate, including Compose stability implications.
Codex code review closeout: local dirty changes, PR branch vs main, parallel tests.
Code Review Expert: Perform in-depth code reviews using context-isolated subagents, covering security vulnerabilities, performance optimizations, and production reliability
Use this when you need to run static analysis with cppcheck, clang-tidy, or GCC analyzer on embedded C/C++ code, or perform MISRA-C compliance checks.
Fix a known bug in the Rock RMS codebase. Guides Claude through root cause analysis, minimal correct fix, and a release-note commit message. Use when the user says "fix this bug", "bugfix", "this is broken", "debug this", describes a bug with file paths or issue numbers, or pastes an error/stack trace with intent to fix. Also use when a bug is found by another skill (e.g. /review-conversion, /check) and the user wants it fixed. Do NOT use for: finding bugs (use /check or /review-conversion), adding features, or refactoring.
Improve existing code through safe, behavior-preserving Clean Code refactoring. Use when the user asks to refactor code, clean up messy code, improve readability, simplify structure, reduce duplication, improve naming, review maintainability, or apply Clean Code principles. Do not use for broad architecture redesign unless the user asks for redesign.
Reviews the current local diff or branch at the end of a coding session for high-confidence bugs and repository instruction-file compliance. Use when asked to run `/pr-reviewer` before commit, before push, or before handing changes off for PR creation or update, and when only certain, actionable findings should be reported while style feedback is ignored.
Error handling guidelines for NeMo-RL. Covers exception specificity, minimal try bodies, and else blocks.
Use when writing or refactoring proof-carrying code in MoonBit, especially for Why3-backed specifications, abstraction functions, representation invariants, proof assertions, recursive verified data structures, or reducing trusted proof bridges.
Generates a heat-map and metrics report of a repository based on code complexity, lack of tests, and 'TODO/FIXME' density. Use when you need to identify high-risk areas for refactoring or when planning technical debt reduction sprints.