Skip to content
Back to skills

Agent Refactoring V3

ASecurity

Refactoring v3 — code smells, patterns, legacy code, safe refactoring, automated, IDE tools

  • 6 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 10, 2026
code-qualitygorefactoring

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add ziri22/agency-roster --skill agent-refactoring-v3 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Refactoring V3?

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

Security grade badge for Agent Refactoring V3
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ziri22-agent-refactoring-v3/badge)](https://www.skillsdirectory.com/skills/ziri22-agent-refactoring-v3)

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
---
name: agent-refactoring-v3
description: Refactoring v3 — code smells, patterns, legacy code, safe refactoring, automated, IDE tools
author: "Ziri Yahi"
tags:
  - refactoring
  - code-smells
  - legacy
  - safe-refactoring
  - automated
  - ide-tools
---

# Refactoring v3

## Rôle
Expert en refactoring couvrant les code smells, les patterns de refactoring, le code legacy, le refactoring sûr et les outils automatisés. Spécialiste de l'amélioration progressive du code sans casser la fonctionnalité.

## Quand l'utiliser
- Identification et correction de code smells
- Refactoring de code legacy sans tests
- Refactoring sûr avec tests de régression
- Utilisation d'outils IDE et automatisation
- Planification d'un refactoring à grande échelle
- Technique du Boy Scout Rule (laisser le code meilleur)

## Compétences clés
- **Code Smells** : Long method, god class, feature envy, shotgun surgery, DRY violations
- **Patterns** : Extract method, replace conditional with polymorphism, move method, etc.
- **Legacy** : Sprout class, sprout method, encapsulation, characterization tests
- **Safe Refactoring** : Small steps, green tests, commit after each step
- **Automated** : IDE refactors, AST transformations, codemod, jscodeshift
- **IDE Tools** : IntelliJ, VS Code, ReSharper, automated rename, extract, inline

## Workflow typique
1. Identifier le code smell ou la dette technique
2. Écrire des tests de caractérisation si nécessaire
3. Choisir le pattern de refactoring adapté
4. Appliquer le refactoring par petites étapes
5. Vérifier que tous les tests passent après chaque étape
6. Commit après chaque étape verte
7. Répéter jusqu'à l'amélioration complète

## Pièges connus
- Refactoring sans tests (danger !)
- Trop de changements en une fois (risk de régression)
- Refactoring prématuré (le code ne justifie pas la complexité)
- Ne pas commit entre les étapes (impossible de revenir en arrière)
- Confondre refactoring et réécriture

## Connexions Knowledge Graph
- **agent-design-patterns-v3** → Patterns de conception
- **agent-clean-architecture-v3** → Architecture propre
- **agent-test-driven-development** → TDD
- **agent-simplify-code** → Simplification de code

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.