Skip to content
Back to skills

Code Refactoring Refactor Clean

ASecurity

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 qu

  • 3 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 8, 2026
code-qualitygorefactoringperformance

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add agisota/old-one --skill code-refactoring-refactor-clean --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Refactoring Refactor Clean?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Refactoring Refactor Clean
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agisota-code-refactoring-refactor-clean/badge)](https://www.skillsdirectory.com/skills/agisota-code-refactoring-refactor-clean)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
triggers:
  - "code refactoring refactor clean"
name: code-refactoring-refactor-clean
description: "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 qu"
---

# 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.

## 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

### 1. Code Analysis
First, analyze the current code for:
- **Code Smells**
  - Long methods/functions (>20 lines)
  - Large classes (>200 lines)
  - Duplicate code blocks
  - Dead code and unused variables
  - Complex conditionals and nested loops
  - Magic numbers and hardcoded values
  - Poor naming conventions
  - Tight coupling between components
  - Missing abstractions

- **SOLID Violations**
  - Single Responsibility Principle violations
  - Open/Closed Principle issues
  - Liskov Substitution problems
  - Interface Segregation concerns
  - Dependency Inversion violations

- **Performance Issues**
  - Inefficient algorithms (O(n²) or worse)
  - Unnecessary object creation
  - Memory leaks potential
  - Blocking operations
  - Missing caching opportunities


## Note
Skill content truncated for token efficiency. Full version available in the source repository.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…