thermo-nuclear-code-quality-review

Reviews code changes for structural regressions, file-size growth, and spaghetti branching.

3|Updated Apr 8, 2025
One-click install
npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill thermo-nuclear-code-quality-review-zanzythebar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thermo-nuclear-code-quality-review
Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/thermo-nuclear-code-quality-review
Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill thermo-nuclear-code-quality-review-zanzythebar

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 leaky 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 rearranging them. - Boundary and Type Cleanliness Enforcement: Questions unnecessary casts, optionality, thin wrappers, and logic placed in the wrong layer. - Use Case: Before approving a large pull request, run this review to get prioritized, high-conviction feedback on maintainability issues with explicit actionable remedies and a strict approval bar. ## Quick Start Ask the AI to run a thermo-nuclear code quality review on the current branch's changes and list the top structural issues with suggested restructurings.

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 returns prioritized findings with concrete restructuring suggestions rather than cosmetic nits.

What does a thermo-nuclear 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 or casts, and missed opportunities to delete complexity through restructuring.

When should I use a deep maintainability review instead of a standard review?

Use it when a change touches core architecture, grows large files, or adds branching to busy code paths. Standard reviews catch bugs; this review catches structural debt that makes the codebase harder to reason about over time.

Does this review approve code that simply works correctly?

No. Correct behavior is not sufficient for approval. The review blocks approval when there are structural regressions, unjustified file-size growth, spaghetti branching, or obvious missed opportunities for dramatic simplification.

What are the limitations of a strict maintainability review?

It focuses on structure and maintainability, not runtime correctness, security vulnerabilities, or performance profiling. Pair it with testing and security analysis for complete coverage of a change.