Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- RefactorRestructure existing code without changing its behavior — extract, rename, inline, split, deduplicate, reshape — with tests holding behavior fixed before and after. Scoped to structure only: no new features, no bug fixes, no behavior changes. Use when the user says "refactor", "clean up the structure", "extract this", "split this file", "untangle", or "restructure".Votes: 0GitHub stars: 84
- Refactoring ProSystematic refactoring: safe transformations, strangler patterns, characterization tests, and large-scale change management. Use when improving code structure without changing behavior.Votes: 0GitHub stars: 2
- Refactor CleanupFor when a piece of code has grown messy and needs a proper cleanup pass — extra abstraction, duplicated logic, confusing structure. Most relevant in src/state, src/features, and src/components.Votes: 0GitHub stars: 2
- RefactorAnalyzes code for smells and structural issues, proposes a safe refactoring plan, and executes it with test verification. Use when code is hard to read, maintain, or extend.Votes: 0GitHub stars: 7
- Code Quality RefactoringImprove maintainability and structure while preserving behavior using framework-agnostic refactoring principles.Votes: 0GitHub stars: 3
- RefactorerRestructure code into clean architecture — separate concerns, raise modularity, reduce coupling, behavior unchanged — applying the repo's evolving `refactorer` role (.claude/roles/refactorer.md). Use when the user says "/roles:as refactorer", "refactor X", "untangle this module", or "clean this up without changing behavior".Votes: 0GitHub stars: 9
- Refactoring PatternsImprove code structure without changing behavior — the discipline of small, named, test-backed moves. Extract function/variable, inline, rename, replace conditional with polymorphism, introduce parameter object, guard clauses. Recognize smells, refactor safely, avoid big-bang rewrites.Votes: 0GitHub stars: 9
- Refactoring SafelyChange the shape of code without changing what it does — get a test harness under it first, move in reversible steps, and keep the refactor out of the change that alters behaviour. Use before restructuring, renaming across files, or untangling something to make a feature possible.Votes: 0GitHub stars: 6
- RefactoringUse for behavior-preserving restructuring: extract, move, split, deduplicate, plan a refactor, or migrate an implementation behind an unchanged contract. Baseline tests, small steps, revert-on-red. Do NOT use for requested behavior or API-contract changes (including new return/error semantics), even when called a "refactor"; use the normal implementation workflow with regression tests and update affected callers together. Also exclude bug fixes (root-cause when stubborn), performance work (le...Votes: 0GitHub stars: 28
- Am Agent Code RefactorImprove code structure, performance, and maintainability through systematic refactoring. Specializes in legacy modernization and technical debt reduction. Use PROACTIVELY for code quality improvements and architectural evolution.Votes: 0GitHub stars: 24
- Refactoring PatternsSafe transformations — same behavior, better structure.Votes: 0GitHub stars: 4
- Thalarch RefactorBehavior-preserving refactoring protocol for simplifying, restructuring, modularizing, or modernizing existing code without silently changing externally observable behavior. Use for non-trivial cleanup, decomposition, abstraction changes, package/module moves, or legacy modernization where regression risk matters.Votes: 0GitHub stars: 2
- Book Refactoring MiniRefactoring (Martin Fowler) — Condensed rules — key principles distilled. Use when asked to apply Refactoring principles or review code against Refactoring standards.Votes: 0GitHub stars: 3
- Refactor SafelyUse when restructuring existing code without intending to change its behavior — extracting functions, renaming across files, splitting modules, or swapping an implementation. Makes the agent pin current behavior with tests first, change in small verified steps, and prove behavior is unchanged, so a "cleanup" never silently breaks something.Votes: 0GitHub stars: 2
- RefactoringImprove code structure while pinning and proving unchanged externally observable behavior.Votes: 0GitHub stars: 2
- Refactor Hashgraph OnlineExecute one behavior-preserving structuralVotes: 0GitHub stars: 3
- Nw Progressive RefactoringProgressive L1-L6 refactoring hierarchy, 22 code smell taxonomy, atomic transformations, test code smells, and Fowler refactoring catalogVotes: 0GitHub stars: 615
- RefactorSystematic code refactoring to improve maintainability without changing behavior. Use when asked to \"refactor this\", \"clean up this code\", \"improve code quality\", \"simplify this\", \"reduce complexity\", or \"eliminate code smells\". Always preserves existing behavior.Votes: 0GitHub stars: 4
- RefactorБезопасный рефакторинг маленькими шагами без изменения поведения. Используй, когда просят отрефакторить, упростить, разделить модуль, убрать дублирование или почистить код.Votes: 0GitHub stars: 35
- 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