refactoring

Cyclomatic complexity measures decision points in code. Reduce it by applying refactoring patterns like extract function to split logic, early returns to simplify branching, or switch extraction to consolidate conditionals. Linters flag high complexity; use this Skill's decision tree to select and apply the appropriate pattern.

Storifying separates orchestration logic from leaf logic to reduce cognitive load in complex functions. Extract function splits a single function into smaller, focused helpers. Storifying targets coordination complexity; extract function targets length and responsibility.

Review your linter output to identify the complexity issue—cyclomatic, cognitive, or readability. The Skill provides a decision tree: use storifying for orchestration overhead, extract type for primitive-heavy parameters, extract function for long logic blocks, or switch extraction for nested conditionals.

Yes. After applying a refactoring pattern, re-run your linter to confirm complexity metrics decreased and re-run tests to ensure behavior is unchanged. The Skill implements a decision-driven workflow that includes verification with lint and tests.

Extract type converts primitive parameters and returns into typed domain concepts. Instead of passing multiple booleans or strings, create a dedicated type. This improves readability, type safety, and reduces function signature cognitive load.

Avoid refactoring when tests are absent or brittle, since verification becomes unreliable. Prioritize test coverage first. Also defer refactoring stable, rarely-modified code unless it blocks new features or introduces maintenance risk.