Repository navigation
chore: version skills - #1
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 2, 2026 12:23
1eb0f8c to
eb67f11
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.2.0
Minor Changes
#551
697d4ceThanks @mattpocock! - Add Codex metadata alongside each skill's Claude Code frontmatter so the set works in both harnesses without generated copies.agents/openai.yamlbeside everySKILL.mdwith Codex UI metadata (interface.display_name,interface.short_description).policy.allow_implicit_invocation: false, the Codex analog ofdisable-model-invocation: true, so Codex excludes it from implicit invocation while explicit$skillinvocation still works..agents/invocation.md,CLAUDE.md, and the promoted-bucket READMEs.AGENTS.mdas a symlink toCLAUDE.mdso Codex reads the same repo instructions.#488
cdec9f6Thanks @mattpocock! - Reword how theprototypeskill handles its artifacts around a single idea: the prototype is a primary source. Rather than being deleted once it's answered its question, the prototype is captured as runnable evidence on a throwaway branch (prototype/<name>) out of main, with a context pointer to it left on the implementation issue — so the main branch keeps only the validated decision while the exploration stays findable. The answer (verdict + question) is still captured durably in an issue/ADR/commit.#536
42a5b70Thanks @mattpocock! - Ship the skill set as a native Claude Code plugin. The repo is now its own single-plugin marketplace, so you can subscribe to the promoted skills as a managed, read-only bundle instead of copying editable files:.claude-plugin/plugin.jsongains full marketplace metadata (version, description, author, license, keywords) and a sibling.claude-plugin/marketplace.jsonlists the plugin.skills.shremains the universal installer (and the path for Codex and other harnesses today); a native Codex plugin is deferred — see.agents/adr/0002-ship-as-a-claude-code-plugin.mdfor why.#538
2602257Thanks @mattpocock! - Wayfinder now burns research tickets down with subagents instead of leaving them parked for a separately-launched session.Research stays a real ticket type — it's a genuine shared blocker that downstream decisions hang on, and that dependency is exactly what the frontier's blocking edges exist to render. What changes is how it's resolved: because research is AFK, charting doesn't stop and read it. After creating the tickets, the charting session fires a
/researchsubagent for each research ticket to burn it down in parallel, capturing the findings on a throwawayresearch/<name>branch with a context pointer. Research tickets are the one exception to one ticket per session.#533
45afd80Thanks @mattpocock! - Add a YAGNI scoping filter to theimprove-codebase-architectureskill's Explore step. Instead of scanning the whole repo evenly, it now scopes to where change is actually landing: if you name a direction it takes it, otherwise it reads the last ~20 commit messages to bias exploration toward actively-developed paths. A deepening opportunity in code nobody touches is a refactor you'll never cash in — the leverage only pays off where you keep editing — so the report stops tidying dormant corners of the repo.Patch Changes
#535
e74fee8Thanks @mattpocock! - Make/ask-mattclued-up about/wayfinder— the heaviest, most cognitively demanding flow.The router now sharpens the two routing mistakes people most often make with wayfinder:
/grill-with-docs, not here./to-spec(which collapses the map's linked decisions into a buildable plan) rather than looping the map straight into/implement. Straight-to-/implementis only for efforts that turned out genuinely small.#502
44eed54Thanks @mattpocock! - Make/setup-matt-pocock-skillsfriendlier and align the local-markdown tracker with the current spec.triageskill is installed, and then as a single recommended-yes question ("keep the default triage labels?") instead of an override interrogation. Whentriageisn't installed, the section — anddocs/agents/triage-labels.md— are skipped.docs/agents/issue-tracker.mdlater..scratch/<feature>/issues/<NN>-<slug>.md— never a single combinedtickets.md./to-ticketsand the local issue-tracker template now agree, and the spec file isspec.md(notPRD.md) to match/to-spec.Docs pages for
setup-matt-pocock-skillsandto-ticketsre-synced.#532
170ad48Thanks @mattpocock! - Rewordgrillingfor general use. Its description and body no longer scope the interview to a software plan: "this plan" → "this", "enact the plan" → "act on it", and "exploring the codebase" → "exploring the environment". The technique is unchanged; it now reads as a stress-test of any plan, decision, or idea.#534
7d694b7Thanks @mattpocock! - Name the/wayfinderunit a decision ticket.People kept reading a wayfinder ticket as an ordinary implementation ticket — a slice of a build to execute — when wayfinder uses them as decision tickets: questions whose resolution is a decision. The skill description and its opening line now introduce "decision ticket" (and say what makes it one), and the
ask-matt/ engineering README wayfinder blurbs and the docs page match — while "ticket" stays the everyday word once the term is established.CONTEXT.mdrecords Decision ticket as a domain term so the "avoid: ticket" guidance no longer contradicts wayfinder's deliberate use of the word.