Safety-railed orchestration for Claude Code: plans behind an approval gate, routes to specialist plugins, tests and security-reviews every change, and stages the result - never commits, never touches production.
Skill Claude CodeCodex
The bundled two-axis code review — use to review a change for quality and spec-fit before it is staged and handed off. Trigger on 'review this change/branch/PR', 'code review', 'is this sound', 'does this match the ticket', or as the orchestrator's Stage 3 review step. It reviews the diff along two independent axes…
Skill Claude CodeCodex
The decision-making ringmaster for any software task. Use at the START of essentially any build, change, fix, or review request, and whenever a request is vague ("help me build X", "add Y", "fix this", "make it better"). Covers new/updated frontends, new/changed features, writing/updating/pruning tests, databases…
Skill Claude CodeCodex
The ownership review - use when a developer must take 100% responsibility for a code change written largely by AI and wants to genuinely understand and stand behind it before shipping. Trigger on 'review this branch/PR', 'code review', 'help me own this code', 'I have to be responsible for this', 'sign off on this…
Skill Claude CodeCodex
Write brutally thorough, fully-traceable test scenarios from a requirement — a Jira/Confluence (or Trello/Linear/Azure DevOps/GitHub Issues) source of truth — BEFORE any test code, then a self-contained HTML/CSV coverage report. This is the requirements-first counterpart to the Test Architect: it trusts the spec and…
Skill Claude CodeCodex
Acts as a Principal Test Architect to plan, write, prune, run, and hand off automated tests for any codebase in any language or framework — never touching production code, never committing, never running against production. Use whenever the user wants to add, fix, expand, refactor, or review tests for a feature, bug…