code-refactor-analyzer
Analyzes codebase for refactoring needs, generates todo reports, and validates completion
When & Why to Use This Skill
The Code Refactor Analyzer is a specialized developer tool designed to streamline codebase maintenance and evolution. It automates the process of identifying technical debt and refactoring needs by analyzing repository context against new requirements. By generating structured todo reports and providing automated completion validation, it helps engineering teams manage complex migrations, improve code quality, and maintain a clear roadmap for architectural improvements.
Use Cases
- Legacy Code Migration: Automatically identify and plan the transition from outdated patterns, such as migrating from class-based components to functional components, with specific file-level tasks.
- Feature Impact Analysis: Evaluate how new feature requirements will affect the existing codebase and generate a comprehensive checklist of necessary modifications to ensure system integrity.
- Technical Debt Management: Scan the repository to find complex or redundant code sections and create a prioritized refactoring roadmap to improve long-term maintainability.
- Progress Tracking for Large Refactors: Use the state-aware validation feature to monitor the completion status of ongoing refactoring tasks across multiple sessions and team members.
| name | code-refactor-analyzer |
|---|---|
| description | Analyzes codebase for refactoring needs, generates todo reports, and validates completion |
Code Refactor Analyzer
This skill helps developers identify code that needs refactoring based on new requirements, generates actionable todo lists, and tracks completion progress.
Capabilities
- Requirement Analysis: Understand user requirements and identify potential code impacts
- Code Impact Analysis: Analyze repository to find code lines that may be affected by the requirement
- Todo Report Generation: Create structured todo lists with specific code locations and tasks
- Completion Validation: Check if previously generated todo items have been completed
- State Management: Automatically detects if this is the first use (generate report) or subsequent use (check completion)
Input Requirements
- User Requirement: Description of the new feature, change, or refactoring need
- Repository Context: Claude Code should have access to the codebase (via open repository)
- Optional Parameters:
- Specific file paths to focus on
- Priority levels for tasks
- Deadline constraints
Output Formats
- First Use: Generates a todo report file at
.claude/code_refactor_report/[requirement]-[date].md - Subsequent Use: Provides completion validation report showing:
- Completed items (checked off)
- Pending items
- New items that may have been added
- Interactive Guidance: Step-by-step suggestions for refactoring
How to Use
"Analyze the codebase for implementing user authentication and identify what needs to be refactored" "Check if the todo items from yesterday's refactoring plan have been completed" "Generate a refactoring plan for migrating from class-based components to functional components"
Scripts
code_analyzer.py: Main analysis engine that identifies impacted codereport_manager.py: Handles todo report generation and completion validationstate_manager.py: Manages skill state (first use vs subsequent use)
Best Practices
- Clear Requirements: Provide specific, detailed requirements for better analysis
- Repository Access: Ensure Claude has access to the codebase before using this skill
- Incremental Refactoring: Focus on small, manageable sections rather than entire codebase
- Regular Validation: Use the completion check feature regularly to track progress
- Documentation: Add comments to refactored code explaining the changes
Limitations
- Requires Claude to have access to the repository files
- Analysis is based on code patterns and may not catch all edge cases
- Cannot automatically fix code - provides guidance only
- Works best with well-structured codebases
- May produce false positives for complex refactoring scenarios