Menu
Dispatch independent adversarial reviews for ZFC, ZFC leveling, and root-cause-first without duplicating their standards.
| name | code-standards |
| description | Dispatch independent adversarial reviews for ZFC, ZFC leveling, and root-cause-first without duplicating their standards. |
Use this skill to dispatch code, diff, PR, or proposed-implementation review against the repo's core standards. This is a pointer/dispatch skill: reference the source skills below instead of duplicating their standards.
Load the relevant source skills by path and treat them as authoritative.
These live at ~/.claude/skills/ (user-scope, shared across all repos) and are
mirrored under .codex/skills/ as pointer files. Skill discovery resolves
personal skills before project skills.
.claude/skills/zero-framework-cognition/SKILL.md (/zfc).claude/skills/zfc-leveling-roadmap/SKILL.md (/zfclevel).claude/skills/root-cause-first/SKILL.md (/root-cause-first)Agent tool with subagent_type: thermo-nuclear-code-quality-review (/thermo)/zfc, /zfclevel, /root-cause-first, and /thermo./thermo lane uses subagent_type: thermo-nuclear-code-quality-review
(NOT a bash command). Pass: diff summary, file list, working dir.Return a concise report:
## Code Standards Report
Scope: <file, diff, PR, or task>
- ZFC: PASS/WARN/FAIL - <evidence>
- ZFC leveling: PASS/WARN/FAIL - <evidence or permitted N/A caveat>
- Root-cause-first: PASS/WARN/FAIL - <evidence or permitted N/A caveat>
- Thermo: PASS/WARN/FAIL - <evidence or structural blockers>
Blockers:
- <line-level issue and required fix>
Next checks:
- <tests, evidence, or review steps needed>
If there are no blockers, say so explicitly and list any residual risks. Do not mark any of the four lanes as skipped.
Use when proving, rejecting, or deleting backend adjustment registry entries with real LLM evidence and independent disabled-adjustment worktrees.
Use when spawning, steering, or auditing Agent Orchestrator workers, especially when the user specifies exact AO parameters such as codex, runtime, project, claim-pr, or PR targets.
Checklist for dispatching AO workers — python venv, commit discipline, branch drift, and post-push CodeRabbit verification
Use when dispatching work through the Hermes gateway with /claw, especially when the task may resolve slash commands or hand off into AO worker orchestration.
Run the Dark Factory DOT pipeline runner against a goal. Slash command: /factory. Implements StrongDM's Attractor pattern as an external Python runner — .dot files are the versioned artifact, sealed holdouts live in a separate repo, every step is recorded to CXDB, and the Healer clusters failures into diagnoses. Use when you want the goal_harness idea executed as a reproducible external pipeline instead of in-Claude subagent dispatch.
Run disk usage analysis and cleanup preview on the local Mac. Always validate snapshot coverage before quoting. Never delete without user approval.