Thermo Nuclear Code Quality Review

Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.

9 stars 1 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add Oreo992/thermo-nuclear-code-quality-review --skill thermo-nuclear-code-quality-review

Manual install

git clone --depth 1 https://github.com/Oreo992/thermo-nuclear-code-quality-review.git /tmp/thermo-nuclear-code-quality-review
mkdir -p ~/.claude/skills
cp -r /tmp/thermo-nuclear-code-quality-review/. ~/.claude/skills/thermo-nuclear-code-quality-review

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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** about code structure. Do not merely identify local cleanup opportunities. Actively search for "code judo" moves: restructurings that preserve behavior while making the implementation dramatically simpler, smaller, more direct, and more elegant.

## Core Prompt

Start from this baseline:

> Perform a deep code quality audit of the current branch's changes.
> Rethink how to structure / implement the changes to meaningfully improve code quality without impacting behavior.
> Work to improve abstractions, modularity, reduce Spaghetti code, improve succinctness and legibility.
> Be ambitious, if there is a clear path to improving the implementation that involves restructuring some of the codebase, go for it.
> Be extremely thorough and rigorous. Measure twice, cut once.

## Non-Negotiable Additional Standards

Apply the baseline prompt above, plus these explicit review rules:

0. **Be ambitious about structural simplification.**
   - Do not stop at "this could be a bit cleaner."
   - Look for opportunities to reframe the change so that whole branches, helpers, modes, conditionals, or layers disappear entirely.
   - Prefer the solution that makes the code feel inevitable in hindsight.

Read the full skill on GitHub

Details

Skill name: thermo-nuclear-code-quality-review
Repository: Oreo992/thermo-nuclear-code-quality-review
Repo updated: 31 July 2026

FAQ

What does the Thermo Nuclear Code Quality Review skill do?

How do I install the Thermo Nuclear Code Quality Review skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Oreo992/thermo-nuclear-code-quality-review --skill thermo-nuclear-code-quality-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Thermo Nuclear Code Quality Review popular?

It lives in Oreo992/thermo-nuclear-code-quality-review, which has 9 GitHub stars and 1 forks.

Related skills

Ask Codex

bookSiYi1412/ask-codex

TRIGGER when: user requests implementation work, repo exploration, data/log inspection, broad codebase search, impact analysis, verification-heavy shell work, or explicitly mentions Codex ("用 codex 做", "让 codex 执行", "ask codex to...", "use codex", "delegate to codex"). Also trigger for heavy internal subtasks that Claude Code might otherwise offload to a lightweight model/Haiku. DO NOT TRIGGER when the task is primarily user-facing product judgment, architecture choice, git/PR/release operations, or requires multi-turn clarification before useful work can begin. This skill routes work between

Software Development

Session Wrap

leonsong09/session-wrap

Use when the user wants to wrap up the current coding session, summarize the current session before ending work, document learnings, decide what to commit, or says 总结会话, 会话总结, 收尾, 会话收尾, 结束会话, 总结本次会话.

Software Development

Codewiki

ekuttan/codewiki

Generate a structured product knowledge base from codebase scanning. Creates a codewiki/ folder with architecture docs, user flows, API reference, service maps, and more. Also generates CLAUDE.md. Handles single repos, monorepos, and multi-repo microservices. Use when asked to document a project, generate a knowledge base, map architecture, create onboarding docs, or set up CLAUDE.md for a codebase.

Software Development

Project Daily Summary

leonsong09/project-daily-summary

Use when the user wants a same-day Codex work summary grouped by project folder or repository, combining today's Codex sessions, extracted plans, completed items, commits, and uncommitted changes, or says 项目日报, 日报, 今日工作总结, 按项目总结今天, 总结今天所有 Codex 会话, 总结今天会话+提交+未提交改动.

Software Development

Coding Workflow

w93139/coding-workflow

Guide implementation, bug fixes, scripts, and small projects through a proportionate brief, scoped changes, fresh verification, and independent read-only review. Use when Codex is asked to change code; keep tiny edits lightweight and do not activate for explanation-only or review-only requests.

Software Development

Product Requirements Review

fourierwang66666/product-requirements-review

Conducts structured product requirements review from idea to design doc. As PM asks clarifying questions; analyzes essence (problem, audience, real demand, business logic); researches competitors and data; as CTO assesses technical feasibility and Vibecode cost/time; then proposes creative, shortest-path solutions (smart, non-generic, with unique value or cold-start); makes go/no-go; if go, produces concept, name, architecture, user flows, system design (Vibecode-oriented), design references, and full design document. Principles: no process for its own sake, challenge ideas directly, common se

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.