Teach agents to author changeset files directly (SF-15)#303
Closed
alexgrozav wants to merge 1 commit into
Closed
Conversation
The changeset policy existed only as a review-time nudge and pointed at `pnpm ci:changeset`, the interactive prompt headless agents cannot drive. Add a concrete "Authoring a changeset" how-to (when, publishable vs ignore list, file format, bump selection, examples) to the near-universal styleframe-verification skill, and repoint the team-protocol changeset bullet away from the interactive command. SF-15.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
1 participant
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.
Summary
Agents knew changesets were required (definition of done, review nudges) but the only authoring instruction pointed at
pnpm ci:changeset— the interactivechangesetprompt, which headless agents cannot drive. So the step was routinely skipped and only caught at review.This adds a positive, actionable authoring path to the skills every implementing seat carries.
Changes
styleframe-verificationskill — new "Authoring a changeset" section: when one is needed (publishableengine/*,theme,tooling/*with the exact npm names), the ignore list that needs none, and a step-by-step for writing the.changeset/<area>-<topic>.mdfile directly — filename convention, frontmatter package+bump lines, bump selection (patch/minor/major, with major gated on Alex's sign-off), body voice, single- and multi-package examples, andpnpm changeset statusas the check. Also surfaced in the skilldescriptionfor discovery.styleframe-team-protocolskill — repointed the Changesets bullet away from the interactivepnpm ci:changesetto "write the file directly," cross-referencing the verification skill.No product code, tests, or docs touched — skills only.
Note
Multica reads skills at import time, not from git — these lessons go live only after the affected skills are re-imported post-merge.
Closes SF-15.