wiggum-refactor

To reduce technical debt after multiple PRs, run a post-hoc module analysis to identify recurring patterns, spec deviations, and simplification opportunities. This process surfaces prioritized refactoring recommendations grounded with file:line citations and authoritative spec references.

The best way to detect code deviations is to perform an analysis that compares your implementation against authoritative specs. This highlights mismatches with concrete file:line citations, revealing exactly where the code diverges from the intended standard.

You can extract reusable code patterns by analyzing modules to identify recurring structures and conventions. This analysis suggests consolidations to standardize in a library or spec, and can optionally create Kanban tasks to track the work.

You should run a code simplification analysis during cleanup cycles or after a feature has touched the same module across multiple PRs. This timing ensures accumulated technical debt and structural inconsistencies are addressed before they compound.

Yes, you can generate Kanban tasks directly from technical debt analysis. The analysis produces prioritized refactoring recommendations with evidence, and includes optional Kanban task creation to track the identified simplification work.