Thermo-Nuclear Code Quality Review

Use this skill for an unusually strict review focused on implementation quality, maintainability, abstraction quality, and codebase health.

Above all, this skill should push the reviewer to be ambitious inside the agreed mission. Actively search for "code judo" moves that make the patch dramatically simpler, smaller, more direct, and more elegant. Structural opportunities outside the mission are follow-ups, not automatic blockers or implementation work.

Scope Governor

This skill is self-contained. Before review, capture the demonstrated failure or requested outcome, acceptance criteria, explicit non-goals, and expected footprint (files, approximate changed lines, and planned new concepts).

Classify every concern:

1. Mission blocker: acceptance remains unmet.
2. Patch regression: the patch creates a concrete new failure.
3. Mandatory safety: a concrete security, authorization, privacy, or data-loss risk.
4. Follow-up: a valuable maintainability improvement outside this mission.
5. Non-finding: speculative, duplicate, stale, pre-existing, or unsupported.

Only the first three categories block the current patch. A cleaner adjacent architecture can be worth doing without belonging in this change.