Skills (mattpocock) for Codex

Skills (38)

• ask-matt — Ask which skill or flow fits your situation. A router over the skills in this repo.
• code-review — 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/spec asked for?). Runs both reviews…
• codebase-design — 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…
• diagnosing-bugs — Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
• domain-modeling — Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
• grill-with-docs — A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
• implement-spec — Implement the result of /to-spec and /to-tickets in code.
• implement — Implement a piece of work based on a spec or set of tickets.
• improve-codebase-architecture — Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
• pr — Use when writing a PR body.
• prototype — Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
• research — Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
• retro — Conduct a retrospective on a coding session.
• setup-matt-pocock-skills — Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
• tdd — Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
• to-spec — Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
• to-tickets — Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
• triage — Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
• wayfinder — Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
• wizard — Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover…
• chief-of-staff — Pursue a long-running goal in a single session by co-ordinating subagents.
• claude-handoff — Hand the current conversation off to a fresh background agent that picks up the work immediately.
• loop-me — Grill me about specs for the workflows I want to build, within this workspace.
• setup-ts-deep-modules — Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.
• writing-beats — Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
• writing-fragments
• writing-shape
• git-guardrails-claude-code
• migrate-to-shoehorn — Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
• scaffold-exercises
• setup-pre-commit
• grill-me — A relentless interview to sharpen a plan or design.
• grilling
• handoff — Compact the current conversation into a handoff document for another agent to pick up.
• teach
• to-questionnaire
• wait-what
• writing-for-agents