earth-rumble
From the author
Toph's Earth Rumble review. The champion takes on every challenger at once and nothing gets past her. Use to review a diff, a branch, a PR, or a design for correctness bugs, breaking changes, security holes, devex breaks, feature-flag leaks, and maintainability. Runs a correctness review and a metalbending quality review in parallel, verifies every finding, and returns one blunt, severity-ranked verdict. Use for thermos, /thermos, thermo nuclear, thermonuclear, /thermo-nuclear-review, double review, deep review, "review this", "audit this", or "is this safe to merge".
Install
npx skills add tmcfarlane/team-avatar --skill earth-rumble -a claude-code
Installs to .claude/skills/earth-rumble/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- metalbendingtmcfarlane/team-avatarToph's metalbending for a strict code quality review. Everyone said metal could not be bent, until Toph felt the specks of earth still trapped inside it and bent the whole thing through them. Use to find the impurities in a rigid-looking structure, such as spaghetti conditionals, files sprawling past 1000 lines, wrappers that buy nothing, and logic in the wrong layer, and to push for the code judo move that makes the change dramatically simpler. Use for thermo-nuclear code quality review, /thermo-nuclear-code-quality-review, deep code quality audit, maintainability review, or "how could this be simpler".Planning★ 111
- thermo-nuclear-reviewmichael-denyer/pstack-claudeComprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.Engineering★ 3.6K
- lie-detectortmcfarlane/team-avatarToph's lie detector for multi-model adversarial review. She feels a heartbeat through the ground and knows when someone is lying, so a change that only claims to work does not fool her. Use for interrogate, /interrogate, adversarial review, multi-model review, "challenge this", "stress test this code", "find blind spots", "tear this apart", or a contested design before it ships. Several reviewers on different models challenge the change independently, and the lead sorts their findings into act on, consider, noted, and dismissed. Never applies changes.Testing★ 111
- full-reviewarcasilesgroup/ai-engineeringRun every review skill at once — build-check, then design-check, code-audit, security-audit, a11y-audit and perf-audit fanned out across parallel agents — and merge them into one deduplicated, severity-ranked report. Use when asked for a full/complete review, to review everything before shipping or merging, or to run all the checks.Engineering★ 62
- reviewhashgraph-online/awesome-codex-pluginsThe pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; with no diff, it reports project health. A bug-hunting code review complements this review and does not replace it. Also use for 'show status', 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Modes, named as the first word: drift for staleness detection, deep for a full documentation audit, closeout to close a finished feature, experience to capture a repeated pattern. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.Engineering★ 1.4K
- thermosmichael-denyer/pstack-claudeLaunch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug/security and code-quality branch audits.Security★ 3.6K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in