File size: 1,537 Bytes
292d92c |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 |
Plan and execute repository refactoring while maintaining functionality.
Your task:
1. Analyze current repository structure:
- File organization
- Code architecture
- Naming conventions
- Dependencies
- Technical debt
2. Identify refactoring needs:
- Poor separation of concerns
- Duplicated code
- Unclear naming
- Circular dependencies
- Outdated patterns
3. Create refactoring plan:
```markdown
## Refactoring Plan
### Goals
- Improve code organization
- Reduce technical debt
- Enhance maintainability
### Proposed Changes
1. Restructure folders:
- Move utilities to src/utils/
- Separate components from pages
- Create dedicated config directory
2. Code improvements:
- Extract repeated logic into utilities
- Rename unclear variables/functions
- Break down large files
3. Update dependencies:
- Remove unused packages
- Update outdated libraries
- Fix security vulnerabilities
### Risk Assessment
- Breaking changes: [None/Low/Medium/High]
- Test coverage: [%]
- Rollback plan: [Strategy]
```
4. Execute refactoring:
- Make changes incrementally
- Test after each change
- Update imports and references
- Fix broken paths
- Update documentation
5. Verify functionality:
- Run tests
- Check for broken references
- Validate build process
- Test key features
Seek user input before major structural changes. Maintain repository functionality throughout refactoring.
|