chore: version skills

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

mattpocock-skills@1.3.0

Minor Changes

• #1120 2aecca1 Thanks @mattpocock! - Graduate implement-spec into the Engineering bucket, so it ships in the Claude Code plugin, gets a docs page, and is routed by ask-matt as the parallel alternative to per-ticket implement.

  implement-spec (user-invoked) implements a whole spec in one run. It reads the tickets as a task graph, runs implementer subagents in their own worktrees across the ready frontier, and lands everything on one integration branch, closing out with code-review. Ahead of graduating:

  • The goal is now the integration branch, not a PR. A draft PR opens only when the issue tracker closes work through PRs or you ask for one, and only after the first merge (a branch with no commits ahead of main can't open one). Without a PR, the tickets are resolved the way the tracker closes work.
  • It points at the issue tracker like its siblings, telling you to run /setup-matt-pocock-skills when none has been provided, rather than silently defaulting to gh.
  • Each implementer confirms its worktree is based on the integration branch, builds its ticket with tdd, and merges the integration tip into its own branch before reporting done, so each merge is a fast-forward.

• #1120 2aecca1 Thanks @mattpocock! - Graduate pr into the Engineering bucket, so it ships in the Claude Code plugin, gets a docs page, and is routed by ask-matt as the PR-body close-out.

  pr (model-invoked) is the shape a pull request body should take: a summary as the smallest visual that makes the change clear (pseudocode, a call tree, a file tree, Mermaid, a diff), before/after evidence that it works, and a merge-danger call (one-way or two-way door, plus blast radius). The Summary visuals are adapted from Dex Horthy's show-me, credited in the skill's CREDITS.md.

• #1120 2aecca1 Thanks @mattpocock! - Graduate retro into the Engineering bucket, so it ships in the Claude Code plugin, gets a docs page, and is routed by ask-matt as the last step of the main flow, after code-review.

  retro (user-invoked) looks back at a coding session and suggests changes to the agent's environment rather than the code: navigation pointers, automated checks, coding standards, steering files, tool economy, information access. It classifies each coding-standards finding first: a mechanical violation gets a deterministic check (a linter rule, a pre-commit hook, or a CI job), and CODING_STANDARDS.md is kept for genuine judgement calls. A repo with no guardrail at all is a finding in its own right.

• #1120 daa01d8 Thanks @mattpocock! - Remove the resolving-merge-conflicts skill. It's no longer needed, and nothing replaces it: the agent works through an in-progress merge or rebase conflict without a dedicated skill. It leaves the Claude Code plugin, the README and the ask-matt router. Its docs page at https://aihero.dev/skills-resolving-merge-conflicts stays up, marked archived.

• #1120 006a52b Thanks @mattpocock! - Rename the CONTEXT.md/CONTEXT-MAP.md domain-doc convention to GLOSSARY.md/GLOSSARY-MAP.md everywhere the skills read and write it (domain-modeling, grill-with-docs, improve-codebase-architecture, setup-matt-pocock-skills, triage, tdd, diagnosing-bugs, ask-matt, codebase-design, wait-what, pr), plus the docs pages and this repo's own root glossary.

  If you have an existing CONTEXT.md (or CONTEXT-MAP.md) from before this change, git mv it to the new name: the skills only look for GLOSSARY.md/GLOSSARY-MAP.md going forward.

Patch Changes

• #848 f02e2ed Thanks @mattpocock! - domain-modeling: trigger on discussing codebase terminology and on writing or editing a GLOSSARY.md or an ADR directly, replacing the narrower "pin down domain terminology or a ubiquitous language" / "record an architectural decision" phrasing. Also drops the "another skill needs to maintain the domain model" caveat, since that's the invoking skill's job to state explicitly, not this description's.

• #911 4f28947 Thanks @mattpocock! - Quote the description front matter in to-spec, code-review, setup-matt-pocock-skills, writing-fragments, writing-shape, and wait-what. An unquoted colon-space left over from the em-dash sweep in #905 made each block invalid YAML, so skills.sh skipped all six during discovery and they couldn't be listed or installed via npx skills.

• #917 85f83d3 Thanks @mattpocock! - grilling: update the round template so consecutive questions are separated by a horizontal rule (---) instead of running together.

• #879 d419977 Thanks @mattpocock! - grilling: remove em-dashes from SKILL.md, replacing them with colons and semicolons so the instructions read as plain text.

• #905 e6e9577 Thanks @mattpocock! - Remove every em-dash from the repo's prose (docs, SKILL.md files, ADRs, README.md, scripts, JSON/YAML metadata), hand-rewriting each sentence with a comma, colon, period, parentheses, or conjunction rather than mechanically substituting the character. CLAUDE.md/AGENTS.md now says not to reintroduce them.

• #878 e3e547b Thanks @mattpocock! - Standardize cross-skill invocation on an explicit "call the Skill tool" instruction instead of bare /skill-style prose, across code-review, diagnosing-bugs, grill-with-docs, grill-me, improve-codebase-architecture, tdd, to-spec, to-tickets, triage, and wayfinder.

  • A skill that names another skill in prose ("run the /grilling skill") does not reliably cause it to load. This is the documented rough edge behind grill-with-docs's most-reported problem. Naming the tool directly (Call the Skill tool with "grilling") is intended to raise the hit rate. Dropping the leading / also makes the instruction harness-neutral rather than less: it no longer assumes Claude Code's trigger syntax.
  • A step needing more than one skill now says so as multiple calls ("Call the Skill tool twice, for grilling and domain-modeling"), not one call carrying two names.
  • Documents the convention in .agents/invocation.md for future skills to follow.

• #880 1dab982 Thanks @mattpocock! - Stop skills from trying to reach user-invoked skills through the Skill tool: fix cross-skill references that violated the "no other skill can call it" invariant in .agents/invocation.md, in to-spec, wayfinder, to-tickets, triage, code-review, and diagnosing-bugs.

  • to-spec, wayfinder, to-tickets, triage, and code-review each carried a precondition ("...run /setup-matt-pocock-skills if not") that PR #878 rewrote into a literal Call the Skill tool with "setup-matt-pocock-skills" instruction. setup-matt-pocock-skills is user-invoked, so none of these skills (user-invoked or model-invoked) can call it. Reworded all five as instructions for the agent to tell the human to run it instead.
  • diagnosing-bugs's Phase 6 post-mortem hand off to improve-codebase-architecture (also user-invoked) the same way, from an autonomous, often-unattended bug-fixing flow with no human in the loop to catch the failed call. Removed the hand-off outright rather than softening it, since it rarely fired in practice. Phase 6 is now "Cleanup" only; the mechanical checklist is untouched.
  • Added a carve-out paragraph to .agents/invocation.md's "Dependencies between them" section: the Call the Skill tool with "name" convention only applies when the named skill is model-invoked. This is the section PR #878 introduced without reconciling it against the user-invoked/model-invoked invariant stated eight lines above it; the gap is most of why this bug reached six call sites instead of one.

  Fixes #453.

• #904 594f0f8 Thanks @mattpocock! - wait-what: follow GLOSSARY-MAP.md to the right GLOSSARY.md when a repo indexes multiple contexts that way instead of keeping a single root GLOSSARY.md.