tdd
Use short test-first cycles to add or change observable behavior.
npx skills add mattpocock/skills --skill tddBuild features, investigate defects and make changes easier to review.
Start with the smallest behavior change you can verify. Use architecture guidance when the structure itself is limiting the change.
Use short test-first cycles to add or change observable behavior.
npx skills add mattpocock/skills --skill tddReproduce a defect, isolate its cause and verify the fix with a regression check.
npx skills add mattpocock/skills --skill diagnosing-bugsFind modules with tangled responsibilities and plan boundaries that simplify future changes.
npx skills add mattpocock/skills --skill improve-codebase-architectureReview a proposed change for regressions, missing coverage and maintainability issues.
npx skills add mattpocock/skills --skill code-reviewBuild a small prototype to answer a technical or product question.
npx skills add mattpocock/skills --skill prototypeCapture decisions, changed files and outstanding tests so another developer can continue the work.
npx skills add mattpocock/skills --skill handoffNo skill in this category has a full write-up yet.
Agent-written code fails in a narrow, predictable way: it does the thing you asked and also changes two files you did not mention. These six skills are arranged against exactly that. tdd keeps the change small enough to see; diagnosing-bugs forces a reproduction before a fix; code-review reads the diff for what you did not ask for; handoff writes down what is still open so the next session does not re-decide it. prototype and improve-codebase-architecture are the two you reach for less often and are the ones most likely to be run too early, because both feel productive while producing very little you can merge. A workable order for a real task is: reproduce, write the failing test, change the smallest thing that makes it pass, review the diff, hand off. Skip the first two and you get a patch that passes on your machine.
Run the tests before you read the diff, not after: a green suite tells you the change did what it claimed, and the diff tells you what else it touched. Then read the diff for edits you did not ask for — renames, formatting, a dependency bump nobody mentioned. That is the failure mode of every agent-written change, and code-review is the skill that catches it if you give it the task description as context. For diagnosing-bugs, keep the failing case as a regression test before you accept the fix; a fix you cannot reproduce the bug against is a guess.
tdd if the behaviour is clear enough to write a test for. diagnosing-bugs if you have a failure but not a cause. improve-codebase-architecture only when the structure itself is what is slowing you down — it is the slowest of the six and the easiest to run too early.
They are six skills from one author's engineering set, and they are written to be chained rather than picked from: reproduce the defect, write the test, make the change, review the diff, hand off what is left. Installing one and expecting the rest of the workflow is the usual mistake.
It reviews a proposed change for regressions, missing coverage and maintainability, and returns findings. It does not run your suite — you do that — and it does not approve or merge anything. Treat its output as the review comments of a careful colleague who has read the diff but not your codebase history.
Same as every skill here: run the install command on the row, or copy the folder to ~/.claude/skills/name/SKILL.md, where name is the skill's folder. The path must end at SKILL.md — an extra folder level on top is the usual reason a skill never activates.