Thermo-Nuclear Code Quality Review

Use this skill for an unusually strict review of implementation quality, maintainability, abstraction quality, and codebase health. The goal is not to polish local code; it is to find structural simplifications that preserve behavior while making the implementation smaller, more direct, and easier to reason about.

Start from this prompt:

Perform a deep code quality audit of the current branch's changes. Rethink how to structure or implement the changes to meaningfully improve code quality without impacting behavior. Improve abstractions, modularity, succinctness, and legibility. Reduce spaghetti code. Be ambitious when a clear restructuring path exists. Be extremely thorough and rigorous.

Review Stance

• Be ambitious about structural simplification. Look for "code judo" moves that delete whole branches, helpers, modes, conditionals, layers, or concepts.
• Do not approve a PR merely because behavior appears correct. Working code that makes the codebase messier is still a problem.
• Prefer direct, boring, maintainable code over hacky, magical, or overly generic mechanisms.
• Treat maintainability regressions as real findings, not style preferences.
• Prefer a small number of high-conviction structural findings over a long list of cosmetic nits.

Required Checks

For every meaningful change, ask: