How does the skill handle missing test coverage?

If tests are missing, the skill recommends adding behavior-driven tests first using a testing skill before attempting any structural changes to the code.

Why does this skill emphasize behavior-driven tests?

Behavior-driven tests focus on what the code does rather than how it does it. This allows the implementation to be changed during refactoring without breaking the tests, ensuring functional integrity.

What is the core principle of this refactoring skill?

The core principle is that refactoring changes the internal structure of the code without changing its external behavior. if behavior changes, it is considered a rewrite, not a refactor.

When is it appropriate to stop refactoring?

Refactoring should stop when the code is clear, duplication is eliminated, types are explicit, and all tests pass. Avoid over-abstracting or optimizing without measurable benefits.

Refactoring Code

Name: Refactoring Code
Author: rileyhilliard

byrileyhilliard

•

開発者ツール

Improves code structure and maintainability while preserving functional behavior through a systematic five-phase verification process.

概要

The Refactoring Code skill provides a rigorous framework for cleaning up codebases without introducing regressions. It guides the user through five distinct phases: understanding current behavior, establishing behavior-driven test coverage, identifying code smells like complexity and duplication, planning incremental changes, and executing with continuous verification. By prioritizing clarity over cleverness and emphasizing that behavior must remain unchanged, this skill helps developers transform legacy or messy code into clean, modular, and type-safe systems.

主な機能

Incremental execution strategy with continuous verification steps
Guidance on behavior-driven test verification to prevent regressions
62 GitHub stars
Structured 5-phase refactoring workflow for safe code evolution
Identification of code smells including deep nesting and magic numbers
Pre-defined mapping of common code smells to specific refactoring solutions

ユースケース

Simplifying overly complex functions with deep nesting and high cyclomatic complexity
Eliminating code duplication by extracting logic into shared, testable utilities
Modernizing legacy code by improving naming conventions and adding explicit TypeScript types

概要

主な機能

Incremental execution strategy with continuous verification steps
Guidance on behavior-driven test verification to prevent regressions
62 GitHub stars
Structured 5-phase refactoring workflow for safe code evolution
Identification of code smells including deep nesting and magic numbers
Pre-defined mapping of common code smells to specific refactoring solutions

ユースケース

Simplifying overly complex functions with deep nesting and high cyclomatic complexity
Eliminating code duplication by extracting logic into shared, testable utilities
Modernizing legacy code by improving naming conventions and adding explicit TypeScript types