thermo-nuclear-code-quality-review

Audit pull requests for structural code quality issues and simplification opportunities.

3|1|Updated Nov 5, 2015

Search Tags:#code quality #code review #refactoring #maintainability #technical debt #pull request audit #abstraction quality

Ready to run

npx skills add https://github.com/Flowm/dotfiles --skill thermo-nuclear-code-quality-review-flowm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: thermo-nuclear-code-quality-review
Source: https://github.com/Flowm/dotfiles/tree/main/home/.agents/skills/thermo-nuclear-code-quality-review
Command: npx skills add https://github.com/Flowm/dotfiles --skill thermo-nuclear-code-quality-review-flowm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard code reviews often only catch minor stylistic issues and miss critical structural maintainability problems, leading to accumulating technical debt, bloated files, and tangled spaghetti code that slows down future development.

Core Features & Use Cases

Ultra-Strict Maintainability Audits: Evaluates code changes against rigorous standards for abstraction quality, file size, and architectural alignment, going beyond superficial style checks.
Code Judo Identification: Actively searches for restructuring opportunities that preserve behavior while dramatically simplifying implementation, deleting unnecessary complexity instead of just rearranging it.
Use Case: Ideal for teams running pull request reviews that need to prevent structural regressions, enforce file size limits, and eliminate tech debt before it accumulates in the codebase.

Quick Start

Use the thermo-nuclear-code-quality-review skill to audit the latest pull request for structural code quality issues and missed simplification opportunities.

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 prevent structural code quality regressions during a pull request audit?▼

Ultra-strict code reviews prevent structural regressions by auditing pull requests for file size limits, abstraction quality, and architectural boundary adherence to eliminate spaghetti code and technical debt.

What is the best way to reduce technical debt in a maintainability review?▼

Reduce technical debt in a maintainability review by identifying restructuring opportunities that preserve behavior while dramatically simplifying implementation, deleting unnecessary complexity instead of rearranging it.

How do I enforce file size limits and architectural boundary adherence in code reviews?▼

Apply ultra-strict maintainability audits to code changes to enforce file size limits and architectural boundary adherence, preventing tangled spaghetti code and ensuring structural alignment.

Does this code review approach check for abstraction quality or just superficial styling?▼

This code review approach evaluates abstraction quality and structural maintainability, going beyond superficial stylistic checks to identify structural regressions and bloated files that slow down future development.

Can I use this for a codebase health check on an existing software engineering project?▼

Yes, you can use this for a codebase health check on existing software engineering projects to identify structural code quality regressions and enforce strict maintainability standards for long-term code health.