thermo-nuclear-code-quality-review

Reviews branch changes for structural regressions, file-size growth, and spaghetti-condition complexity.

136|8|Updated May 9, 2026
One-click install
npx skills add https://github.com/Sma1lboy/rove --skill thermo-nuclear-code-quality-review-sma1lboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: thermo-nuclear-code-quality-review
Source: https://github.com/Sma1lboy/rove/tree/main/.agents/skills/thermo-nuclear-code-quality-review
Command: npx skills add https://github.com/Sma1lboy/rove --skill thermo-nuclear-code-quality-review-sma1lboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often rubber-stamp working implementations that quietly degrade maintainability through file sprawl, ad-hoc conditionals, and unnecessary abstractions. This Skill enforces an unusually strict review standard that pushes for structural simplification rather than accepting code that merely works. ## Core Features & Use Cases - Structural Regression Detection: Flags PRs that push files past 1000 lines, add scattered special-case branches, or leak feature logic into shared modules. - Code-Judo Restructuring Push: Actively searches for reframings that delete whole layers of complexity instead of just rearranging them. - Boundary and Type Cleanliness Checks: Questions unnecessary casts, optionality, thin wrappers, and logic placed in the wrong layer or package. - Use Case: Before merging a large feature branch, run this review to get high-conviction, prioritized feedback on maintainability issues with explicit approval blockers and actionable remedies. ## Quick Start Ask the AI to run a thermo-nuclear code quality review on the current branch's changes before merging the pull request.

Frequently Asked Questions about thermo-nuclear-code-quality-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a strict code quality review on a pull request?▼

Invoke this review on the current branch's changes to audit abstraction quality, file size, and branching complexity. It produces prioritized findings with explicit approval blockers and concrete restructuring suggestions.

What does a maintainability-focused code review check for?▼

It checks for files crossing 1000 lines, ad-hoc conditionals added to existing flows, feature logic leaking into shared modules, unnecessary wrappers and casts, and missed opportunities to delete complexity through restructuring.

When should I use a strict structural review instead of a standard review?▼

Use it when a change touches core architecture, grows large files, or adds special-case branching. Standard reviews verify behavior; this review blocks merges that preserve avoidable structural complexity even when tests pass.

Does this review approve code that works correctly?▼

No. Correct behavior alone does not meet the approval bar. The review blocks approval when there are structural regressions, unjustified file-size growth, spaghetti branching, or visible opportunities for dramatic simplification.

What kinds of feedback does the review prioritize?▼

It prioritizes structural regressions and missed simplification opportunities first, then branching complexity, boundary and type-contract problems, file-size concerns, and modularity issues. Low-value cosmetic nits are deliberately deprioritized.