WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Run an opt-in strict maintainability review for giant files, spaghetti growth, misplaced logic, weak boundaries, unnecessary abstractions, and missed structural simplifications.
Install Thermo Nuclear Code Quality Review
$ npx skills add AnastasiyaW/codex-claude-code-config --skill thermo-nuclear-code-quality-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config thermo-nuclear-code-quality-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/development/thermo-nuclear-code-quality-review .claude/skills/thermo-nuclear-code-quality-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "thermo-nuclear-code-quality-review" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/development/thermo-nuclear-code-quality-review into .claude/skills/thermo-nuclear-code-quality-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thermo-nuclear-code-quality-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/development/thermo-nuclear-code-quality-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill thermo-nuclear-code-quality-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config thermo-nuclear-code-quality-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/development/thermo-nuclear-code-quality-review .agents/skills/thermo-nuclear-code-quality-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "thermo-nuclear-code-quality-review" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/development/thermo-nuclear-code-quality-review into .agents/skills/thermo-nuclear-code-quality-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thermo-nuclear-code-quality-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill thermo-nuclear-code-quality-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config thermo-nuclear-code-quality-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/development/thermo-nuclear-code-quality-review .cursor/skills/thermo-nuclear-code-quality-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "thermo-nuclear-code-quality-review" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/development/thermo-nuclear-code-quality-review into .cursor/skills/thermo-nuclear-code-quality-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thermo-nuclear-code-quality-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/AnastasiyaW/codex-claude-code-config.git --path skills/development/thermo-nuclear-code-quality-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill thermo-nuclear-code-quality-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config thermo-nuclear-code-quality-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/development/thermo-nuclear-code-quality-review .gemini/skills/thermo-nuclear-code-quality-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "thermo-nuclear-code-quality-review" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/development/thermo-nuclear-code-quality-review into .gemini/skills/thermo-nuclear-code-quality-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thermo-nuclear-code-quality-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install AnastasiyaW/codex-claude-code-config thermo-nuclear-code-quality-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add AnastasiyaW/codex-claude-code-config --skill thermo-nuclear-code-quality-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/development/thermo-nuclear-code-quality-review .github/skills/thermo-nuclear-code-quality-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "thermo-nuclear-code-quality-review" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/development/thermo-nuclear-code-quality-review into .github/skills/thermo-nuclear-code-quality-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thermo-nuclear-code-quality-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill thermo-nuclear-code-quality-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config thermo-nuclear-code-quality-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/development/thermo-nuclear-code-quality-review .opencode/skills/thermo-nuclear-code-quality-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "thermo-nuclear-code-quality-review" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/development/thermo-nuclear-code-quality-review into .opencode/skills/thermo-nuclear-code-quality-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "thermo-nuclear-code-quality-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
thermo-nuclear-code-quality-review- GitHub stars
- 154
- Token cost
- ~891 tokens
- SKILL.md length
- 425 words
- Files
- 1
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run an opt-in strict maintainability review for giant files, spaghetti growth, misplaced logic, weak boundaries, unnecessary abstractions, and missed structural simplifications.
- Works in 6 steps: structural regressions; → missing simplifications with a concrete… → spaghetti or branching growth; → …
- A thermonuclear review
- SKILL.md covers Review Bar, Output, Independence and scope and Gotchas, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Thermo Nuclear Code Quality Review is an agent skill from AnastasiyaW/codex-claude-code-config. 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.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Code quality. The repository describes itself as: Claude Code, Codex, and multi-agent configuration system: principles, hooks, skills, and workflow patterns for AI-assisted development. The licence is MIT.
When your agent uses it
- A thermonuclear review
- Harsh code-quality audit
- Code-judo review
- A file approaching 1000 lines
Example prompts
- “/thermo-nuclear-code-quality-review”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- structural regressions;
- missing simplifications with a concrete alternative;
- spaghetti or branching growth;
- boundary and type-contract problems;
- file shape and decomposition;
- lower-severity readability issues.
What it can do on your machine
Read from SKILL.md and the folder at commit 67709af. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Thermo Nuclear Code Quality Review loads about 891 tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 425 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from AnastasiyaW/codex-claude-code-config at commit 67709af, republished under its MIT licence (© AnastasiyaW). 425 words, ~891 tokens.
Download SKILL.mdSave it as
.claude/skills/thermo-nuclear-code-quality-review/SKILL.md (or your agent's skills folder).- name
- thermo-nuclear-code-quality-review
- description
- 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.
- disable-model-invocation
- true
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?
- Did a cohesive module become more coupled or cross a meaningful shape limit?
- Are wrappers, casts, optionality, and sequential orchestration earning their complexity?
- Does a proposed decomposition reduce what a reader must hold in mind, rather than merely move the same complexity into more files?
A file crossing roughly 1000 lines is a strong signal to inspect decomposition, not an automatic failure. Apply the project's actual shape policy and explain why a split would improve ownership. Do not manufacture a rewrite when the current structure is coherent and the change is small.
Output
Report findings in this order:
- structural regressions;
- missing simplifications with a concrete alternative;
- spaghetti or branching growth;
- boundary and type-contract problems;
- file shape and decomposition;
- lower-severity readability issues.
For each finding include file/line, contract or evidence, user/operator impact,
and a concrete remedy. Separate BLOCKER, ADVISORY, and ACCEPTED decisions.
If no finding survives reachability, materiality, and evidence screening, say so.
Independence and scope
Use a fresh reviewer for non-trivial changes. This review does not replace
focused tests, security proof, or proof-verify; it evaluates maintainability
and architecture. It must not silently edit production code or turn an
advisory concern into a rewrite.
Show full SKILL.md (150 more words)Show less
Gotchas
- Ambition without a contract becomes over-engineering. Keep the selection gate: a sufficient implementation is a reason to stop expanding.
- A line count is a probe, not a universal design law.
- Moving code across files without reducing coupling is not a successful decomposition.
- Passing tests do not erase a material architecture regression, but a style preference without impact is not a blocker.
Troubleshooting
| Symptom | Likely cause | Action |
|---|---|---|
| Review proposes a rewrite for a tiny diff | Scope or trigger was too broad | Limit the review to changed behavior and material risks |
| Many low-value nits | No severity/materiality screen | Keep only findings with evidence and an actionable remedy |
| File is large but coherent | Threshold treated as a verdict | Record ACCEPTED with rationale and keep the stable boundary |
| Suggested split adds more indirection | Complexity moved, not removed | Reject it and compare the reader's concepts before/after |
Source
Adapted from Cursor Team Kit's MIT-licensed thermo-nuclear-code-quality-review:
https://github.com/cursor/plugins/tree/main/cursor-team-kit/skills/thermo-nuclear-code-quality-review
© AnastasiyaW, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/development/thermo-nuclear-code-quality-review of AnastasiyaW/codex-claude-code-config.
Open the folder on GitHubat commit 67709af
Compare with similar skills
Thermo Nuclear Code Quality Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Thermo Nuclear Code Quality Review this skillAnastasiyaW/codex-claude-code-config | 154 | — | ~891 | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Ponytail Lazy Developer ModeDietrichGebert/ponytail | 160k | 1 repos | ~873 | Automated safety check: Pass | MIT | |
| Systematic Code Refactoringluongnv89/claude-howto | 42k | — | ~3k | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.4k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Constraint-Driven Developmentaddyosmani/agent-skills | 105k | 2 repos | ~5.2k | Automated safety check: Pass | MIT |
Similar skills
Ponytail Lazy Developer Mode
DietrichGebert/ponytail
Makes the agent pick the laziest solution that works: skip unneeded work, reuse what exists, prefer the standard library and platform features, and keep diffs small.
Systematic Code Refactoring
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
Constraint-Driven Development
addyosmani/agent-skills
Records a project's quality bar in CONSTRAINTS.md and watches diffs for signs an agent quietly weakened it, such as suppressions, skipped tests or lowered thresholds.
Skill Doli Code Review
Dolibarr/dolibarr
Reviews Dolibarr PHP code for compliance with coding standards and security best practices, and fixes identified issues.
More from AnastasiyaW/codex-claude-code-config
All 50 skills in this repoBug Reproducer
AnastasiyaW/codex-claude-code-config
Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix.
Motion Framer
AnastasiyaW/codex-claude-code-config
A skill your agent uses when implementing Motion or Framer Motion in React/JavaScript: interactive UI components, micro-interactions, gestures, layout or page transitions, and scroll-based animation.
Proof Verify
AnastasiyaW/codex-claude-code-config
Plan-based verification - freeze acceptance criteria before building, then verify after with an independent fresh-context agent (the builder must not verify their own work).
Workflow Orchestration
AnastasiyaW/codex-claude-code-config
Написание и запуск Claude Code dynamic workflows (JS-оркестратор субагентов).
Notebooklm Grounded Research
AnastasiyaW/codex-claude-code-config
A skill your agent uses when: NotebookLM, notebooklm MCP, large documentation sets, courses, books, papers, or citation-backed research are mentioned.
Deepseek Provider Contract
AnastasiyaW/codex-claude-code-config
Validate a proposed DeepSeek API integration before any key or project context is sent: check thinking-mode tool-call history, strict-schema assumptions, bounded output, and provider data boundaries.
Related
Categories
Questions about Thermo Nuclear Code Quality Review
What does Thermo Nuclear Code Quality Review do?
Run an opt-in strict maintainability review for giant files, spaghetti growth, misplaced logic, weak boundaries, unnecessary abstractions, and missed structural simplifications. Thermo Nuclear Code Quality Review is an agent skill from AnastasiyaW/codex-claude-code-config. Run an opt-in strict maintainability review for giant files, spaghetti growth, misplaced logic, weak boundaries, unnecessary abstractions, and missed structural simplifications.
When should I use Thermo Nuclear Code Quality Review?
Thermo Nuclear Code Quality Review fits situations like: A thermonuclear review; harsh code-quality audit; code-judo review; A file approaching 1000 lines.
How do I install Thermo Nuclear Code Quality Review in Claude Code?
Run `npx skills add AnastasiyaW/codex-claude-code-config --skill thermo-nuclear-code-quality-review -a claude-code`. Or copy the skill folder (skills/development/thermo-nuclear-code-quality-review in AnastasiyaW/codex-claude-code-config) into .claude/skills/thermo-nuclear-code-quality-review in your project. Claude Code loads it when a task matches its description.
How do I install Thermo Nuclear Code Quality Review in Codex?
Run `npx skills add AnastasiyaW/codex-claude-code-config --skill thermo-nuclear-code-quality-review -a codex`. Or copy the skill folder (skills/development/thermo-nuclear-code-quality-review in AnastasiyaW/codex-claude-code-config) into .agents/skills/thermo-nuclear-code-quality-review in your project. Codex loads it when a task matches its description.
Can I use Thermo Nuclear Code Quality Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AnastasiyaW/codex-claude-code-config --skill thermo-nuclear-code-quality-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/thermo-nuclear-code-quality-review, .gemini/skills/thermo-nuclear-code-quality-review, .github/skills/thermo-nuclear-code-quality-review and .opencode/skills/thermo-nuclear-code-quality-review in your project.
What does Thermo Nuclear Code Quality Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Thermo Nuclear Code Quality Review is instructions for the agent only.
Does Thermo Nuclear Code Quality Review access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Thermo Nuclear Code Quality Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Thermo Nuclear Code Quality Review use?
Thermo Nuclear Code Quality Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Thermo Nuclear Code Quality Review use?
About 891 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Thermo Nuclear Code Quality Review?
Skills that share tags, products or a category with Thermo Nuclear Code Quality Review: WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Ponytail Lazy Developer Mode (DietrichGebert/ponytail, 160k stars), Systematic Code Refactoring (luongnv89/claude-howto, 42k stars) and Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Thermo Nuclear Code Quality Review?
AnastasiyaW (a GitHub user) maintains it in AnastasiyaW/codex-claude-code-config, which has 154 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 9, 2026.
Source: AnastasiyaW/codex-claude-code-config on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.