Pack № 03 · Build

Pro Developer

Sharp tools you call when you need them, from first question to green PR.

Who it's forProfessional engineers who already have a way of working and want their agent to match it. Most tools here wait until you call them: an interview before a design hardens, a clickable map of the code you are about to change, test-first implementation, a disciplined bug hunt and pull requests that get read and get green. One stays on and keeps every change small. No router skill, no forced ceremony.
npx skills add mattpocock/skills@abeeaf95660ba9e8b7c753eb38f441ca707a8823 --skill grill-me grilling tdd codebase-design diagnosing-bugs -g -y && \
npx skills add tt-a1i/archify@8509a3d63e763b4d454ea9aafa1f939545fcb1ea --skill archify -g -y && \
npx skills add DietrichGebert/ponytail@96608e078b2d5ea607c5c3b8b5a54d1c1fba6846 --skill ponytail -g -y && \
npx skills add getsentry/skills@a582c51ee29d0f35e6ac321340796f77d43da733 --skill pr-writer iterate-pr -g -y

Fetches 9 skills from 4 author repos, each pinned to the version we reviewed. Nothing is mirrored. Uses the open-source skills CLI; needs Node.js 22.20 or newer.

What's inside

9 skills. Each card links to its author's repository at the exact version we reviewed.

  1. Grill me 1/9 Requirements Ready Slash command that starts a relentless interview about your plan or design. It only hands over to the grilling skill, which does the work. @mattpocock MIT

    Grill me

    Your entry point for requirements. Type /grill-me before a design hardens and you get questioned until nothing is left assumed.

    Works right away Community · Matt Pocock MIT
    Source mattpocock/skills at abeeaf9
  2. Grilling 2/9 Requirements Ready Interviews you about a plan in rounds, each question with a recommended answer, looks facts up itself and does not act until you confirm a shared understanding. @mattpocock MIT

    Grilling

    The interview itself. grill-me is an empty wrapper without it, and it also answers when you simply ask to be grilled.

    Works right away Community · Matt Pocock MIT
    Source mattpocock/skills at abeeaf9
  3. Archify 3/9 Diagrams Needs app Turns a system description or a real codebase into a checked, standalone HTML diagram you can click through: architecture, workflow, sequence, data flow, ERD and more. @tt-a1i Apache-2.0

    Archify

    Before you change a system you do not know, have the agent trace it and draw it. The result is one HTML file you can click through and send to a colleague.

    Needs an app or CLI Community · tt-a1i Apache-2.0
    Source tt-a1i/archify at 8509a3d
  4. Test-driven development 4/9 Testing Ready Keeps the agent on a red, then green loop: one failing test, minimal code, one slice at a time, with tests at agreed public seams instead of internals. @mattpocock MIT

    Test-driven development

    Test-first work with the rules a strict reviewer would set. Behaviour through public interfaces, one slice per cycle, no tests that pass by construction.

    Works right away Community · Matt Pocock MIT
    Source mattpocock/skills at abeeaf9
  5. Codebase design 5/9 Architecture Ready Gives the agent one vocabulary for module design (module, interface, depth, seam, adapter) and rules for deep modules that are easy to test. @mattpocock MIT

    Codebase design

    The shared vocabulary tdd calls on when an interface is in doubt. Useful alone when you argue about where a seam belongs.

    Works right away Community · Matt Pocock MIT
    Source mattpocock/skills at abeeaf9
  6. Ponytail 6/9 Coding discipline Ready Lazy senior developer mode: the agent solves the whole task with the least new code, reuses what the codebase has and ends each reply with what it skipped or did not check. @DietrichGebert MIT

    Ponytail

    Agents overbuild. This one holds the diff to what the task needs and tells you what it left out. It keeps whatever you ask for, so say in AGENTS.md that spec tests are required.

    Works right away Community · Dietrich Gebert MIT
    Source DietrichGebert/ponytail at 96608e0
  7. Diagnosing bugs 7/9 Debugging Ready Debugs in phases: build one fast command that reproduces the bug, shrink the case, rank testable hypotheses, probe one variable at a time, fix with a regression test. @mattpocock MIT

    Diagnosing bugs

    For the bugs that eat a day. It refuses to theorise until one command reproduces the failure, the step agents like to skip.

    Works right away Community · Matt Pocock MIT
    Source mattpocock/skills at abeeaf9
  8. PR writer 8/9 Pull requests Writes pull request titles and bodies as a short cover note for reviewers: what changed, why it matters and where to look, not a changelog or file list. @getsentry Apache-2.0

    PR writer

    Reviewers want a cover note, not a diff summary. This writes the note and opens the pull request as a draft.

    Community · Sentry Apache-2.0
    Source getsentry/skills at a582c51
  9. Iterate on PR 9/9 Pull requests Loops on an open pull request: reads failed CI logs and review comments, fixes the cause, pushes and repeats until checks pass, then stops at human approval gates. @getsentry Apache-2.0

    Iterate on PR

    Takes the tedious loop off your hands. Failed checks and review comments get fixed and pushed until only human gates remain.

    Community · Sentry Apache-2.0
    Source getsentry/skills at a582c51

Good to know

What you bring

  • The grilling skill from the same repository
  • Node.js 18 or newer
  • Chrome, Chromium or Edge for the browser check
  • The codebase-design skill from the same repository
  • GitHub CLI (gh), signed in to your GitHub account
  • uv to run the bundled Python scripts

Pick one, not both

  • Requirements: grilling and the brainstorming skill from Superpowers do the same job. This pack uses grilling; do not install both.
  • Always-on style: Ponytail and Caveman both set rules for every reply in a session. This pack uses Ponytail because it governs the code and not only the wording; do not run both.
  • Review: this pack leaves code review to the reviewer built into your agent. If you want a skill for it, find-bugs by Sentry reports bugs and security issues on your branch, and code-review by Matt Pocock checks a diff against your standards and the spec but needs his setup skill once per repository. Add one, not both.
  • Pull request text: pr-writer and the pr skill by Matt Pocock answer the same request. This pack uses pr-writer.
  • Refactoring: improve-codebase-architecture by Matt Pocock finds modules worth deepening, but it calls three more skills (codebase-design, grilling and domain-modeling). If you add it, add domain-modeling with it.
  • Install route: the Matt Pocock skills also ship as one Claude Code plugin. Use either the plugin or the single skills, never both, or every skill shows up twice.

Do not combine with

These collections steer the same part of your agent's work and get in each other's way.

Review slipPack № 03
  • Every skill file read in full
  • Pinned to a reviewed version
  • Author and licence on every card
  • Requirements and costs disclosed
  • No sponsored skills inside
Last reviewed
Nov 2026
Reviewed