chore(skills): vendor five mattpocock skills already in the lock - #589
Conversation
`skills-lock.json` has recorded 23 skills for a while, but only the ones a project member actually materialized are committed — 8 of the 13 on disk. These five were installed and left untracked, so every `git status` since carried them and one nearly rode into an unrelated PR. - `ask-matt` — a router over the other skills, so the set stays reachable without every description paying context load. - `implement` — build from a spec or tickets. - `to-spec` / `to-tickets` — turn a conversation into a spec, then split it into tracer-bullet tickets with blocking edges. - `triage` — move issues and external PRs through a state machine of roles. All five are `disable-model-invocation: true`, so they cost NOTHING in context: only a person typing the name can fire them, which is why adding five at once is not five more descriptions in every window. `ask-matt` exists to carry the cognitive load that trade makes — it is the index you read instead of remembering the list. The lock moves three hashes (`ask-matt`, `to-spec`, `to-tickets`) — upstream content that changed and was re-pulled. `implement` and `triage` were already locked at these hashes and only lacked their bodies. Nothing is added or removed from the lock. `.claude` is a symlink to `.agents/`, so this lands once and both names see it. Known: `to-spec`, `to-tickets` and `triage` each expect an issue-tracker and triage-label vocabulary that no config in this repo supplies yet. Until someone runs `/setup-matt-pocock-skills`, those three say so and stop rather than guessing a tracker. `ask-matt` and `implement` work as-is. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 15 minutes Limit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (14)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
3 participants
Five skills that
skills-lock.jsonhas recorded for a while but that were never committed. They sat untracked in every working tree, and one of them nearly rode into #588 by accident — which is what prompted separating them out.What is already true
The lock holds 23 skills. Only the ones a project member actually materialized are on disk (13), and of those, 8 were committed. This adds the missing 5.
ask-mattimplementto-specto-ticketstriageWhy five at once costs nothing
Every one is
disable-model-invocation: true. The description is stripped from the agent's reach, so only a person typing the name can fire them — five more skills is not five more descriptions in every context window. What it does spend is the reader's memory of what exists, andask-mattis precisely the cure for that: one router naming the others and when to reach for each.The lock
Three hashes move —
ask-matt,to-spec,to-tickets— upstream content that changed and was re-pulled.implementandtriagewere already locked at their current hashes and only lacked their bodies. Nothing is added to or removed from the lock, so this does not widen what the repo depends on..claudeis a symlink to.agents/, so the files land once and both names resolve to them.Known gap
to-spec,to-ticketsandtriageeach expect an issue-tracker and triage-label vocabulary that no config in this repo supplies. Until someone runs/setup-matt-pocock-skills, those three say so and stop rather than guessing a tracker — inert, not broken.ask-mattandimplementwork as-is.Verification
make license-checkpasses (exit 0) — these are markdown and YAML, and the gate does not require headers on them. No code, no build inputs, nothing imported at runtime: the files are read by the agent harness only, so the remaining gates have no surface to exercise. Content of all 13 files read before committing.🤖 Generated with Claude Code