Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- refactor-assistantHelps refactor code for better structure, readability, and maintainability. Use when cleaning up code, improving design, or removing technical debt.Votes: 0GitHub stars: 14
- RefactorPoint at a file or folder — get it broken down into focused, testable pieces following enterprise patternsVotes: 0GitHub stars: 4
- RefactoringUse when refactoring Handsontable code - applying SOLID principles, Law of Demeter, plugin extraction, performance optimization, code modernization, and API redesign with backward compatibility preservationVotes: 0GitHub stars: 22,055
- Code RefactoringThe practice of restructuring and simplifying code continuously – reducing complexity, improving design, and keeping codebases clean.Votes: 0GitHub stars: 207
- Refactoring SafelyChange structure without changing behavior, in reversible steps.Votes: 0GitHub stars: 3
- Refactoring SpecialistUse when you need to transform poorly structured, complex, or duplicated code into clean, maintainable systems while preserving all existing behavior.Votes: 0GitHub stars: 25
- Refactoring GuideSafe code transformation - changing structure without changing behavior. From Fowler's catalog to legacy code strategies, knowing when and how to improve code without breaking itUse when "refactor, refactoring, clean up, legacy code, code smell, improve this, restructure, technical debt, rewrite, extract, inline, rename, move method, refactoring, legacy-code, code-smells, transformation, incremental, technical-debt, clean-code" mentioned.Votes: 0GitHub stars: 137
- Va Refactoring Specialist\"Use when you need to transform poorly structured, complex, or duplicated code into clean, maintainable systems while preserving all existing behavior.\".Votes: 0GitHub stars: 25
- RefactorRefactors code for quality and maintainability. Triggers: refactor, clean up, restructure, improve code, modernize.Votes: 0GitHub stars: 177
- Refactoring PatternsGuides expert-level refactoring patterns implementation: refactoring and clean-code decision frameworks, production-ready patterns, and concrete templates for refactoring patterns workflows. Use when the user asks about refactoring patterns, refactoring patterns configuration, or refactoring best practices for refactoring projects. Do NOT use when the user needs a different developer tools capability -- check sibling skills in the developer tools subcategory.Votes: 0GitHub stars: 595
- RefactorSurgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.Votes: 0GitHub stars: 4
- Before You RefactorUse when considering, evaluating, or performing a refactor, restructure, cross-file rename, or cleanupVotes: 0GitHub stars: 24
- RefactorAnalyze code for SOLID violations and suggest targeted improvementsVotes: 0GitHub stars: 6,113
- Java RefactoringRefactoring mechanics for Java: characterisation tests, small reversible steps, what behaviour preservation actually covers, risk classification, and the catalogue — Extract/Inline, Split Phase, guard clauses, Remove Flag Argument, Pull Up and Push Down, Replace Conditional with Polymorphism or sealed types. What to detect is java-code-smells; evolution rules for published APIs are java-api-design. Use when restructuring code without changing behaviour, when a change is needed in code that ha...Votes: 0GitHub stars: 2
- Refactor Legacy CodeModernize and improve legacy codebases while maintaining functionality. Use when you need to refactor old code, reduce technical debt, modernize deprecated patterns, or improve code maintainability without breaking existing behavior.Votes: 0GitHub stars: 327
- RefactoringSystematic refactoring with small-step discipline. Use when user says 'refactor', 'clean up', 'restructure', 'extract', 'rename', 'simplify', or mentions code smells. Enforces one change → test → commit cycle. For structural improvements, NOT style/formatting (use /lint). NOT for adding features or fixing bugs.Votes: 0GitHub stars: 416
- Refactoring PatternsSafe refactoring pattern catalog: code smell taxonomy, transformation techniques, behavior preservation strategies, and metrics tracking.Votes: 0GitHub stars: 157
- Principle RefactoringRefactoring discipline — Fowler's catalog of behavior-preserving moves (Extract Function, Inline Variable, Move Function, Replace Conditional with Polymorphism, Introduce Parameter Object, Extract Class), the smell→move mapping (Long Method, Large Class, Feature Envy, Data Clumps, Primitive Obsession, Shotgun Surgery, Divergent Change, Speculative Generality), the rule of three, characterization-tests-before-touching-legacy, and small-steps-with-green-between discipline. Distinct from princip...Votes: 0GitHub stars: 3
- Fec Refactoring FunctionsUse when behavior-preserving frontend refactoring focuses on function structure, naming, parameters, shared context, or phase boundaries, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.Votes: 0GitHub stars: 21
- Fec Refactoring DataUse when behavior-preserving frontend refactoring focuses on variable meaning, field naming, derived state, or reference/value identity, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.Votes: 0GitHub stars: 21