Code Refactoring Methodology
Reconfiguration process recommendations based on system characteristics:
- diagnostic phase::
- Generate technical debt reports (code duplication/test coverage/complexity analysis) with @code-reviewer
- Identify architectural anti-patterns (e.g. over-coupled modules) with @architect-scanner
- planning stage::
- Calling @refactoring-planner to develop a phased refactoring roadmap
- Use @test-coordinator to ensure that test coverage is not degraded
- Implementation phase::
- Division of labor among domain expert intelligences (e.g., @rails-refactoring-expert handles model layers)
- Mandatory introduction of engineering practices (configured via CLAUDE.md: must contain structured logging/fuses)
- validation phase::
- Autorun @performance-benchmarker comparison metrics
- Synchronizing Architecture Documentation Updates with @docs-generator
Typical case: the system coordinates when transforming a monolithic application to microservices:
- @domain-analyzer delineates boundary contexts
- @api-designner Design Compact
- @circuit-breaker-specialist implantation of resilience mechanisms
This answer comes from the articleClaude 007 Agents: an AI Intelligent Body Orchestration System for Modern Software DevelopmentThe
May not be reproduced without permission:AI productivity tools " What are the best practices for code refactoring with Claude-007-Agents?
English 
简体中文 
日本語 
Deutsch 
Português do Brasil