Loading...
Loading...
Found 510 Skills
Use when working with tdd workflows tdd refactor
Refactor, simplify, or clean up code for improved maintainability without changing business logic
Implement the minimal code needed to make failing tests pass in the TDD green phase.
Analyze Go function lengths within a workspace and generate statistics (p50, p90, p99). Use when you need to audit function complexity, identify long functions, or generate code metrics for Go projects. Only analyzes files matching **/*.go within the current workspace, excluding dependencies.
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.
This skill should be used when making design decisions, evaluating trade-offs, assessing code quality, or when "engineering judgment" or "code quality" are mentioned.
Refactor code to improve clarity and maintainability without changing behavior. Use when improving readability, reducing complexity, or eliminating duplication.
Comprehensive coding standards and best practices for maintainable, consistent software development across multiple languages and paradigms
Use when creating or modifying classes, modules, or functions. Use when feeling pressure to add functionality to existing code. Use when class has multiple reasons to change.
TDD-based code simplification that preserves behavior through tests. Use Red-Green-Refactor cycles to simplify code one test-verified change at a time. **DISTINCT FROM**: General code review or AI rewriting—this skill requires existing tests and only proceeds when tests confirm behavior is preserved. **PROACTIVE**: Auto-invoke when test-covered code has complexity (functions >50 lines, high cyclomatic complexity, duplication) and user wants to simplify it safely. Trigger phrases: 'clean up code', 'make code simpler', 'reduce complexity', 'refactoring help'. **NOT FOR**: Adding features or fixing bugs—use /tdd skill instead.
Simplify code and remove legacy/backcompat shims while preserving behavior. Use when asked to clean up or simplify code.
Dead Code Cleanup and Consolidation Expert. Used to remove unused code, duplicate code, and refactor. Execute analysis tools (knip, depcheck, ts-prune) to identify and safely remove dead code.