improve-codebase-architecture

Run this Skill to walk the codebase for shallow modules, seam leakage, and poor locality, weighted toward recently changed hot spots from git history. It presents each candidate as a before/after diagram in an HTML report with a recommendation strength badge.

A shallow module has an interface nearly as complex as its implementation, so it adds indirection without hiding complexity. Deepening means collapsing wrappers and consolidating responsibility behind one small interface, which becomes the single test surface.

No. The HTML report is written to the OS temp directory as architecture-review-<timestamp>.html and opened in your browser, so nothing lands in the repo. CONTEXT.md and ADRs are only updated during the grilling loop when decisions crystallize.

Candidates that contradict an existing ADR are only surfaced when the friction is real enough to warrant revisiting the decision. They are marked with a warning callout explaining why the ADR is worth reopening, rather than listing every theoretical refactor.

Skip it for code that rarely changes, since deepening pays off by easing future modifications. Also avoid re-suggesting refactors that ADRs already rejected unless new friction justifies reopening the decision.