“Refactoring”

Plan refactors with Ontoly impact and dependency evidence.

Refactor code to improve structure and readability.

Aplicar refactoring cuando el encargo requiera código y contratos actuales.

Safe refactoring workflow using Chain of Small Steps.

Safely restructure code without changing behaviour.

Change structure only while tests stay red-green and behavior holds.

Safe refactoring workflow for Go: behavior-preserving steps, compiler-checked renames, extracting packages, breaking circular dependencies, and strangler…

Guide for code refactoring, use this skill to guide you when user asked to refactor a components or functions and when an implementation of a plan requiring a…

Refactor high-complexity React components in Dify frontend.

Multi-target refactoring orchestrator.

Code refactoring patterns and techniques for improving code quality without changing behavior.

Plan behavior-preserving refactoring with explicit scope, depth and risk choices.

Changing existing code structure without intending to change observable behavior.

Code refactoring best practices based on Martin Fowler's catalog and Clean Code principles (formerly refactoring).

Perform one behavior-preserving refactoring step on a given target.

Apply named refactoring transformations to improve code structure without changing behavior.

End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run affected tests.

Invoke IMMEDIATELY via python script when user requests refactoring analysis, technical debt review, or code quality improvement.

Use when a user explicitly requests Sepia refactor for minimal in-place prose revision.

Behavior-preserving code refactoring.

Audit and fix visual hierarchy, spacing, color, and depth in web UIs.

Refactor code at method, file, or project scope.

Use when a named refactor, rename, move or internal API reshape must keep behavior unchanged, or a shim or compatibility re-export tempts.

Refactor cleanly instead of layering sediment.