mattpocock

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

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.

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.

Migrate test files from `as` type assertions to @total-typescript/shoehorn

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting

Shared vocabulary for designing deep modules

Ask which skill or flow fits your situation. A router over the skills in this repo.

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.

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).

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo

Diagnosis loop for hard bugs and performance regressions