arda/skills
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
skills/skills/engineering/README.md
Matt Pocock 14c13c5bf9 Rename review skill to code-review and promote to engineering 
Rename the in-progress `review` skill to `code-review` and move it from
`skills/in-progress/` into the promoted `skills/engineering/` bucket.

- Add it to `.claude-plugin/plugin.json` and the Model-invoked sections of
  the top-level and Engineering READMEs; drop it from the in-progress README.
- Add a docs page at `docs/engineering/code-review.md`.
- Point `/implement` and its docs at `/code-review`.
- Update the smell-baseline changeset reference; add a changeset for the move.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 12:04:12 +01:00

2.4 KiB
Raw Blame History

Engineering

Skills I use daily for code work.

User-invoked

Reachable only when you type them (disable-model-invocation: true).

  • ask-matt — Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
  • grill-with-docs — Grilling session that also builds your project's domain model, sharpening terminology and updating CONTEXT.md and ADRs inline.
  • triage — Move issues through a state machine of triage roles.
  • improve-codebase-architecture — Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
  • setup-matt-pocock-skills — Configure this repo for the engineering skills (issue tracker, triage labels, domain doc layout). Run once per repo.
  • to-issues — Break any plan, spec, or PRD into independently-grabbable issues using vertical slices.
  • to-prd — Turn the current conversation into a PRD and publish it to the issue tracker.

Model-invoked

Model- or user-reachable (rich trigger phrasing so the model can reach for them).

  • prototype — Build a throwaway prototype to answer a design question: a runnable terminal app for state/logic, or several toggleable UI variations.

  • diagnosing-bugs — Disciplined diagnosis loop for hard bugs and performance regressions: reproduce → minimise → hypothesise → instrument → fix → regression-test.

  • tdd — Test-driven development with a red-green-refactor loop. Builds features or fixes bugs one vertical slice at a time.

  • domain-modeling — Actively build and sharpen a project's domain model — challenge terms, stress-test with scenarios, update CONTEXT.md and ADRs inline.

  • codebase-design — Shared discipline and vocabulary for designing deep modules: small interfaces, clean seams, testable through the interface.

  • code-review — Two-axis review of the diff since a fixed point: Standards (does it follow the repo's coding standards, plus a Fowler smell baseline?) and Spec (does it faithfully implement the originating issue/PRD?), run as parallel sub-agents.