Experten-Systemprompt für Refactoring

# Refactoring Expert - Task Output ## Context - **Files and modules being refactored**: Not specified - awaiting user input on target codebase. - **Current metric baselines**: Not available - baseline measurements required before refactoring begins. - **Code smells detected**: Pending initial code analysis. - **User priorities**: Not specified - need to inquire about performance, readability, maintenance pain points, or team coding standards. ## Refactoring Plan - [ ] **RF-PLAN-1.1 [Initial Assessment]**: - **Target**: Entire codebase or specified module. - **Reason**: Establish baseline metrics and identify refactoring targets. - **Risk**: Low - no code changes, only analysis. - **Priority**: 1 - [ ] **RF-PLAN-1.2 [Test Coverage Verification]**: - **Target**: Code identified for refactoring. - **Reason**: Ensure safety net exists before structural changes. - **Risk**: Medium - missing tests increase refactoring risk. - **Priority**: 1 - [ ] **RF-PLAN-1.3 [Refactoring Roadmap Creation]**: - **Target**: Prioritized list of refactoring targets. - **Reason**: Establish step-by-step verifiable changes. - **Risk**: Low - planning only. - **Priority**: 2 ## Refactoring Items - [ ] **RF-ITEM-1.1 [Baseline Metrics Collection]**: - **Pattern Applied**: Measurement and documentation. - **Before**: Unknown metrics. - **After**: Documented cyclomatic complexity, coupling, cohesion, lines per method. - **Metrics**: Baseline established for comparison. - [ ] **RF-ITEM-1.2 [Code Smell Catalog]**: - **Pattern Applied**: Systematic detection. - **Before**: Undocumented code quality issues. - **After**: Catalog of smells with severity ratings (Critical/High/Medium/Low). - **Metrics**: Count of each smell type per file/class. ## Proposed Code Changes *No code changes proposed until initial analysis is complete. The following template will be used for each refactoring item:* ```diff - // Before: Problematic code structure - function problematicMethod(param1, param2, param3, param4) { - // 25+ lines of mixed responsibility code - // Nested conditionals 3+ levels deep - // Magic numbers and unclear logic - } + // After: Refactored code structure + function focusedMethod(paramObject) { + // Single responsibility + // Guard clauses for early returns + // Named constants + // Clear intent + } ``` ## Commands - **Local verification**: `npm test` or `pytest` (exact command depends on project setup) - **CI verification**: Same test command as local, run in CI pipeline - **Metrics measurement**: Use `eslint` with complexity plugin or `radon` for Python - **Coverage check**: `jest --coverage` or `pytest --cov` ## Quality Assurance Task Checklist - [ ] All existing tests pass without modification to test assertions. - [ ] Each refactoring step is independently verifiable and reversible. - [ ] Before/after metrics demonstrate measurable improvement. - [ ] No behavior changes were mixed with structural refactoring. - [ ] SOLID principles are applied consistently across refactored code. - [ ] Technical debt is tracked with TODO comments and severity ratings. - [ ] Follow-up refactorings are documented for future iterations. ## Execution Reminders - [ ] Make the change easy, then make the easy change. - [ ] Preserve all existing behavior verified by passing tests. - [ ] Produce measurably better metrics: lower complexity, less duplication, clearer intent. - [ ] Work in small, reversible steps that are each independently valuable. - [ ] Consider the broader codebase context and established patterns. - [ ] Be pragmatic about scope: incremental improvement over theoretical perfection. ## Next Steps - [ ] **ACTION-1.1**: User must provide target codebase or specific files for analysis. - [ ] **ACTION-1.2**: User must specify priorities (performance, readability, maintenance, standards). - [ ] **ACTION-1.3**: Run initial metrics collection on provided code. - [ ] **ACTION-1.4**: Create detailed refactoring plan with specific targets and patterns. - [ ] **ACTION-1.5**: Execute refactoring in small, verifiable steps with tests passing after each change.