Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- RefactoringImprove code structure while pinning and proving unchanged externally observable behavior.Votes: 0GitHub stars: 2
- 1698 Refactor C3b949d0Use for mechanical refactors across the codebase — "rename X to Y", "extract this to a helper", "move function to shared module". Performs comprehensive symbol search, updates all imports/exports, verifies with typecheck/tests. Flags ambiguous cases for human review.Votes: 0GitHub stars: 4
- Refactor Hashgraph OnlineExecute one behavior-preserving structuralVotes: 0GitHub stars: 3
- RefactoringUse when restructuring code without changing behavior — extract modules, move classes, redraw dependency boundaries, split or merge files. Behavior-preserving structural changes that make the codebase easier to evolve, distinct from single-file clarity cleanup. Triggers on "refactor structure", "extract module", "move class", "split file", "change dependency", "重构结构", "提取模块", "拆分文件", "改依赖图". Not for single-file clarity cleanup (use simplify), architecture audit producing a design doc (use cod...Votes: 0GitHub stars: 3
- Code RefactoringCode refactoring patterns and techniques for improving code quality withoutVotes: 0GitHub stars: 61
- RefactorEssentialist Refactor Specialist. Reduces complexity without changing behavior using the Mikado Method and Safe Sequence. Use when simplifying a God class, deduplicating a business rule, centralizing scattered permission checks, migrating legacy patterns to modern standards, or performing an atomic cleanup pass on a specific file.Votes: 0GitHub stars: 37
- Safe RefactorRestructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.Votes: 0GitHub stars: 110,002
- RefactoringApply Martin Fowler-inspired refactoring rules when improving existing code structure while preserving observable behavior.Votes: 0GitHub stars: 2,838
- 05 Refactor SafetyRefactor safely: scope, preserve behavior, cut complexity, sequence multi-file refactors, verify the changed surface.Votes: 0GitHub stars: 2
- Refactor RsmdtRefactor, simplify, or clean up code for improved maintainability without changing business logicVotes: 0GitHub stars: 3
- 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
- Csharp RefactoringPerforms safe, behavior-preserving refactoring of C#/.NET code, verified with build, tests, and analyzers. USE FOR: rename or move a symbol/type/file; extract a method/type/interface; inline a wrapper/method/local; merge or consolidate near-identical classes or duplicate helpers; split or modernize C# code; generated/partial declarations; public, serialized, friend-assembly, or multi-targeted contracts; and mixed requests where a feature, bug fix, package/framework upgrade, public nullability...Votes: 0GitHub stars: 485
- RefactoringImprove code structure while verifying unchanged behavior.Votes: 0GitHub stars: 2
- 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
- RefactorImprove existing code through surgical behavior-preserving refactoring. Use this skill when code is hard to understand or maintain, functions or classes are too large, code smells need addressing, adding features is difficult due to structure, or the user asks to clean up, refactor, or improve code without changing behavior.Votes: 0GitHub stars: 2
- Code RefactoringCode refactoring patterns and techniques for improving code quality without changing behavior. Use when cleaning up legacy code, reducing complexity, extracting methods, removing duplication, improving maintainability, planning refactor steps, or matching code smells to safe refactoring patterns.Votes: 0GitHub stars: 2
- 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
- RefactorImprove existing code through surgical behavior-preserving refactoring. Use this skill when code is hard to understand or maintain, functions or classes are too large, code smells need addressing, adding features is difficult due to structure, or the user asks to clean up, refactor, or improve code without changing behavior.Votes: 0GitHub stars: 2