Skill Claude CodeCodex
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
Skill Claude CodeCodex
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Skill Claude CodeCodex
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Skill Claude CodeCodex
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Skill Claude CodeCodex
A relentless interview to sharpen a plan or design.
Skill Claude CodeCodex
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Skill Claude CodeCodex
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Skill Claude CodeCodex
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Skill Claude CodeCodex
Use when changing UI, components, visual polish, buttons, empty states, status indicators, or labels in this MCP note app: always use accessible inline SVG icons and never use emojis or emoji-like decorative text.
Skill Claude CodeCodex
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: