Matt Pocock¶
Vendored from https://github.com/mattpocock/skills. 20 skills.
| Skill | Description |
|---|---|
mattpocock-ask-matt |
Ask which skill or flow fits your situation. A router over the skills in this repo. |
mattpocock-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 (doe… |
mattpocock-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… |
mattpocock-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. |
mattpocock-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. |
mattpocock-grill-with-docs |
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go. |
mattpocock-implement |
Implement a piece of work based on a spec or set of tickets. |
mattpocock-implement-spec |
Implement the result of /to-spec and /to-tickets in code. |
mattpocock-improve-codebase-architecture |
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. |
mattpocock-pr |
Use when writing a PR body. |
mattpocock-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. |
mattpocock-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 ga… |
mattpocock-retro |
Conduct a retrospective on a coding session. |
mattpocock-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. |
mattpocock-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. |
mattpocock-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. |
mattpocock-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 f… |
mattpocock-triage |
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs. |
mattpocock-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 des… |
mattpocock-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… |