code-refactoring-refactor-clean
Refactors code to improve quality, simplify logic, and follow clean code principles.
Install
mkdir -p .claude/skills/code-refactoring-refactor-clean && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1622" && unzip -o skill.zip -d .claude/skills/code-refactoring-refactor-clean && rm skill.zipInstalls to .claude/skills/code-refactoring-refactor-clean
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Identify code smells in complex functions
- →Apply SOLID design principles incrementally
- →Prepare modules for future feature integration
- →Execute small-slice refactoring
- →Verify regression stability via testing
How it works
Follows a defined implementation playbook to assess hotspots and apply small, isolated changes to improve architecture.
Inputs & outputs
When to use code-refactoring-refactor-clean
- →Reduce technical debt
- →Simplify complex functions
- →Apply SOLID design principles
- →Prepare modules for new features
About this skill
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.mdfor detailed patterns and examples.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
When not to use it
- →Simple one-line bug fixes
- →Projects where code refactoring is prohibited
Limitations
- →Does not substitute for human expert review
- →Refactoring plan requires manual verification
How it compares
It enforces incremental, step-by-step verification instead of large-scale, risky code restructuring.
Compared to similar skills
code-refactoring-refactor-clean side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| code-refactoring-refactor-clean (this skill) | 24 | 4mo | No flags | Advanced |
| effective-go | 323 | 9mo | No flags | Beginner |
| solid-principles | 57 | 9mo | No flags | Intermediate |
| typescript-review | 39 | 2mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by sickn33
View all by sickn33 →You might also like
effective-go
openshift
Apply Go best practices, idioms, and conventions from golang.org/doc/effective_go. Use when writing, reviewing, or refactoring Go code to ensure idiomatic, clean, and efficient implementations.
solid-principles
SmidigStorm
Enforce SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) in object-oriented design. Use when writing or reviewing classes and modules.
typescript-review
metabase
Review TypeScript and JavaScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs containing TypeScript/JavaScript code.
ast-grep
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for code patterns, find specific language constructs, or locate code with particular structural characteristics.
serena
massgen
This skill provides symbol-level code understanding and navigation using Language Server Protocol (LSP). Enables IDE-like capabilities for finding symbols, tracking references, and making precise code edits at the symbol level.
typescript
lobehub
TypeScript code style and optimization guidelines. Use when writing TypeScript code (.ts, .tsx, .mts files), reviewing code quality, or implementing type-safe patterns. Triggers on TypeScript development, type safety questions, or code style discussions.