mcpField
C
code-refactoring-refactor-clean

code-refactoring-refactor-clean

github.com/rmyndharisDevelopment2.0k151 installsUpdated 3w ago
Repository

About code-refactoring-refactor-clean

code-refactoring-refactor-clean is a skill for developers improving tangled or hard-to-maintain code. It proposes incremental refactors that preserve behavior, update tests, and keep changes reviewable.

Key features

  1. 01Identify code smells and risky areas
  2. 02Plan incremental refactoring steps
  3. 03Reduce duplication and complexity
  4. 04Preserve behavior during changes
  5. 05Update tests and check regressions

Use cases

  1. 01Cleaning up tangled modules
  2. 02Preparing code for new features
  3. 03Improving testability and consistency
  4. 04Refactoring safely with regression checks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rmyndharis/antigravity-skills --skill code-refactoring-refactor-clean

After installing, type/code-refactoring-refactor-cleanin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

Refactor and Clean Code

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

Use this skill when

  • Refactoring tangled or hard-to-maintain code
  • Reducing duplication, complexity, or code smells
  • Improving testability and design consistency
  • Preparing modules for new features safely

Do not use this skill when

  • You only need a small one-line fix
  • Refactoring is prohibited due to change freeze
  • The request is for documentation only

Context

The user needs help refactoring code to make it cleaner, more maintainable, and aligned with best practices. Focus on practical improvements that enhance code quality without over-engineering.

Requirements

$ARGUMENTS

Instructions

  • Assess code smells, dependencies, and risky hotspots.
  • Propose a refactor plan with incremental steps.
  • Apply changes in small slices and keep behavior stable.
  • Update tests and verify regressions.
  • If detailed patterns are required, open resources/implementation-playbook.md.

Safety

  • Avoid changing external behavior without explicit approval.
  • Keep diffs reviewable and ensure tests pass.

Output Format

  • Summary of issues and target areas
  • Refactor plan with ordered steps
  • Proposed changes and expected impact
  • Test/verification notes

Resources

  • resources/implementation-playbook.md for detailed patterns and examples.

Comments

Markdown supported