Claude Code skills: the curated list

Makes the agent find the root cause of a bug, test failure or unexpected behaviour before it proposes a fix.

Makes the agent write a failing test before any implementation code, for features and bug fixes alike.

Sets up an isolated workspace with git worktrees before feature work or plan execution begins.

Requires the agent to run verification commands and confirm the output before it claims that work is complete or passing.

Writes a step-by-step implementation plan from a spec or requirements before any code is touched.

Guides creating, editing and testing skills before they are deployed.

Tells you which of Matt Pocock's skills or flows fits your situation.

Reviews the changes since a commit or branch on two axes: the repo's coding standards and the originating spec.

Gives the agent a shared vocabulary for designing deep modules, deciding interfaces and making code easier to test.

Runs a diagnosis loop for hard bugs and performance regressions.

Builds and sharpens a project's domain model through a glossary and ADRs.

Interviews you relentlessly to sharpen a plan or design, and writes ADRs and a glossary along the way.

Implements in code what the to-spec and to-tickets skills produced.

Implements a piece of work in code, working from a spec or a set of tickets.

Scans a codebase for chances to deepen modules, shows them in an HTML report, then interviews you about the one you pick.

Writes the body of a pull request so that reviewers can follow the change.

Builds a throwaway prototype to answer a design question about a state model, logic or UI.

Investigates a question against primary sources and saves the findings as a Markdown file in the repo.

Runs a retrospective on a coding session to capture what went well and what did not.

Configures a repo for Matt Pocock's engineering skills: issue tracker, triage labels and domain doc layout.

Builds features and fixes bugs test-first with the red-green-refactor loop.

Turns the current conversation into a spec and publishes it to the project's issue tracker, without a further interview.

Breaks a plan or spec into tracer-bullet tickets with their blocking relationships, published to the issue tracker.

Moves issues and external pull requests through triage: categorise, verify and write briefs an agent can act on.