earth-rumble
De la autor
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".
Instalare
npx skills add tmcfarlane/team-avatar --skill earth-rumble -a claude-code
Se instalează în .claude/skills/earth-rumble/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 83
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- 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".Planificare★ 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.Inginerie★ 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.Testare★ 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.Inginerie★ 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.Inginerie★ 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.Securitate★ 3.6K
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te