Repository navigation
chore: version skills - #112
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
November 16, 2026 23:27
ce9869c to
9c83694
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 16, 2026 23:32
9c83694 to
7207120
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
github-agent-workflow@1.11.2
Patch Changes
file-github-issuesnow listsrunnerlike every other pipeline skill, and the protocol's Defaults table names it.explore-github-repopasses its runner name on when it dispatches the skill, so the runner no longer falls back tounknown. The runner prompts are regenerated.merge-safetynames its how-section## Process, like every other skill, instead of## Workflow. Nothing cited the old name.agent-workflow-protocolandpipeline-guidenow open with## Contract(kind: reference), like every other skill, instead of carrying it near the end. The protocol's Inputs names both input forms (free text and key-value pairs) and says each is none.runner-promptsno longer ends with a## Neversection, the legacy shape that contracts replaced. Its three rules (invent no input, editreferences/prompts.mdonly throughnpm run sync, run no pipeline skill) are now the last step of Process.npm run validatenow checks four rules it let through: the contract is the first section of every skill, reference skills included; a reference skill may not keep a## Never,## Resultor other folded section; every skill that runs has a## Processsection; and every pipeline skill listsrunnerandunattended. The protocol's Contracts section now definestypesand states these rules. A heading inside a code fence no longer counts as a section.