Loading...
Loading...
Found 79 Skills
Run a formal, multi-dimensional code review of a pull request. Reads the PR diff, classifies change types, dispatches parallel reviewers by dimension (correctness, consistency, docs-sync, plus conditional security/edge-cases/UX/performance/structure/maintainability), and synthesizes findings into an actionable punch list. Use when the user asks to review a PR, run /deep-review, mark a PR as ready for review, or requests a formal/thorough code review.
Restructures existing code to improve readability, maintainability, and performance without changing external behavior. USE WHEN: Restructuring code without changing behavior, extracting methods/classes, removing duplication, applying design patterns, improving code organization, reducing technical debt. DO NOT USE: For bug fixes (use /debugging), for adding tests (use /testing), for new features (implement directly). TRIGGERS: refactor, restructure, rewrite, clean up, simplify, extract, inline, rename, move, split, merge, decompose, modularize, decouple, technical debt, code smell, DRY, SOLID, improve code, modernize, reorganize.
Use when designing modules, APIs, and system architecture requiring independent, non-overlapping components where changes in one don't affect others.
Practical guidance for writing, refactoring, and reviewing fast, reliable, and maintainable Rust code.
SOLID design principles for .NET. Use when designing classes, interfaces, and object relationships. Ensures maintainable, testable, and extensible code.
Code simplification for clarity and maintainability. Use PROACTIVELY after code is written or modified to refine recently changed files.
Perform a code review with linting, standards checking, and priority-ranked findings
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
This rule enforces the Don't Repeat Yourself principle to avoid code duplication and improve maintainability.
Refactor overly large code units into smaller, more focused components. Use when code has grown too large or complex.
Used to audit codebases to ensure their naming complies with established terminology and specifications. This Skill should be used when you need to enforce a project's 'Ubiquitous Language', identify deviations in method/variable/parameter naming, and propose modification suggestions.
Analyzes code comments for accuracy, completeness, and long-term maintainability. Identifies misleading comments, comment rot, and documentation gaps. Triggers: After adding documentation, before finalizing a PR, when reviewing comments. Examples: - "Check if the comments are accurate" -> verifies comments match code behavior - "Review the documentation I added" -> analyzes new comments for quality - "Analyze comments for technical debt" -> finds outdated or misleading comments - "Are my docstrings correct?" -> validates documentation accuracy