Refactor Method Complexity Reduce

1---2name: refactor-method-complexity-reduce3description: 'Refactor given method `${input:methodName}` to reduce its cognitive complexity to `${input:complexityThreshold}` or below, by extracting helper methods.'4---5 6# Refactor Method to Reduce Cognitive Complexity7 8## Objective9Refactor the method `${input:methodName}`, to reduce its cognitive complexity to `${input:complexityThreshold}` or below, by extracting logic into focused helper methods.10 11## Instructions12 131. **Analyze the current method** to identify sources of cognitive complexity:14   - Nested conditional statements15   - Multiple if-else or switch chains16   - Repeated code blocks17   - Multiple loops with conditions18   - Complex boolean expressions19 202. **Identify extraction opportunities**:21   - Validation logic that can be extracted into a separate method22   - Type-specific or case-specific processing that repeats23   - Complex transformations or calculations24   - Common patterns that appear multiple times25 263. **Extract focused helper methods**:27   - Each helper should have a single, clear responsibility28   - Extract validation into separate `Validate*` methods29   - Extract type-specific logic into handler methods30   - Create utility methods for common operations31   - Use appropriate access levels (static, private, async)32 334. **Simplify the main method**:34   - Reduce nesting depth35   - Replace massive if-else chains with smaller orchestrated calls36   - Use switch statements where appropriate for cleaner dispatch37   - Ensure the main method reads as a high-level flow38 395. **Preserve functionality**:40   - Maintain the same input/output behavior41   - Keep all validation and error handling42   - Preserve exception types and error messages43   - Ensure all parameters are properly passed to helpers44 456. **Best practices**:46   - Make helper methods static when they don't need instance state47   - Use null checks and guard clauses early48   - Avoid creating unnecessary local variables49   - Consider using tuples for multiple return values50   - Group related helper methods together51 52## Implementation Approach53 54- Extract helper methods before refactoring the main flow55- Test incrementally to ensure no regressions56- Use meaningful names that describe the extracted responsibility57- Keep extracted methods close to where they're used58- Consider making repeated code patterns into generic methods59 60## Result61 62The refactored method should:63- Have cognitive complexity reduced to the target threshold of `${input:complexityThreshold}` or below64- Be more readable and maintainable65- Have clear separation of concerns66- Be easier to test and debug67- Retain all original functionality68 69## Testing and Validation70 71**CRITICAL: After completing the refactoring, you MUST:**72 731. **Run all existing tests** related to the refactored method and its surrounding functionality742. **MANDATORY: Explicitly verify test results show "failed=0"**75   - **NEVER assume tests passed** - always examine the actual test output76   - Search for the summary line containing pass/fail counts (e.g., "passed=X failed=Y")77   - **If the summary shows any number other than "failed=0", tests have FAILED**78   - If test output is in a file, read the entire file to locate and verify the failure count79   - Running tests is NOT the same as verifying tests passed80   - **Do not proceed** until you have explicitly confirmed zero failures813. **If any tests fail (failed > 0):**82   - State clearly how many tests failed83   - Analyze each failure to understand what functionality was broken84   - Common causes: null handling, empty collection checks, condition logic errors85   - Identify the root cause in the refactored code86   - Correct the refactored code to restore the original behavior87   - Re-run tests and verify "failed=0" in the output88   - Repeat until all tests pass (failed=0)894. **Verify compilation** - Ensure there are no compilation errors905. **Check cognitive complexity** - Confirm the metric is at or below the target threshold of `${input:complexityThreshold}`91 92## Confirmation Checklist93- [ ] Code compiles without errors94- [ ] **Test results explicitly state "failed=0"** (verified by reading the output)95- [ ] All test failures analyzed and corrected (if any occurred)96- [ ] Cognitive complexity is at or below the target threshold of `${input:complexityThreshold}`97- [ ] All original functionality is preserved98- [ ] Code follows project conventions and standards