Individual skill
thermo-nuclear-code-quality-review
Run an opt-in strict maintainability review for giant files, spaghetti growth, misplaced logic, weak boundaries, unnecessary abstractions, and missed structural simplifications. Use for a thermonuclear review, harsh code-quality audit, code-judo review, or a file approaching 1000 lines. Do not use as an automatic rewrite mandate or for cosmetic cleanup.
skills/development/thermo-nuclear-code-quality-review/SKILL.md
Source commit 849719987d9c0d6ed973bdbce8ed37b266d3b1f3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 214
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- claude Repository topic
- claude-code Repository topic
- llm Repository topic
- machine-learning Repository topic
- prompt-engineering Repository topic
- skills Repository topic
- mcp Repository topic
- agent-harness Repository topic
- harness Repository topic
- marketing Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,563 bytes
Read excerpt
# Strict Code Quality Review
This is an unusually demanding review mode, not an instruction to rewrite code
by taste. Inspect the current diff and surrounding architecture, then report
only high-conviction findings grounded in a contract, reachable behavior, or a
material maintainability risk.
## Review Bar
Ask:
- Can a simpler ownership boundary remove whole branches or concepts?
- Did the diff add ad-hoc flags, special cases, or feature logic to a shared
path instead of using the canonical layer?