thermo-nuclear-code-quality-review

Invoke this skill on the current diff and it audits structural quality, simplification opportunities, and branching complexity. Findings are ordered by severity with concrete file and line references, leading with structural regressions rather than cosmetic nits.

It checks structural regressions, missed simplification paths, spaghetti growth from special-case branches, file-size explosions past 1000 lines, thin wrappers, unnecessary casts or any types, and feature logic leaking into shared modules.

A change that pushes a file from below 1000 lines to above 1000 lines is treated as a presumptive blocker. The reviewer asks whether the code should be decomposed first, relaxing this only when the file remains clearly organized with a strong structural reason.

Avoid it for quick prototypes, throwaway scripts, or early exploratory work where speed matters more than structure. The demanding approval bar can slow iteration when maintainability is not yet the priority.

Findings are ordered structural regressions first, then missed simplifications, spaghetti growth, boundary and type-contract problems, file-size concerns, modularity issues, and legibility last. The review favors a few high-conviction findings over many low-value comments.