Repository navigation
feat: prefix bundled skill descriptions with [yoke] - #10
Merged
Merged
Conversation
staff0rd
enabled auto-merge (squash)
October 28, 2026 04:12
ecakirman
approved these changes
Oct 28, 2026
staff0rd
changed the title
|
🎉 This PR is included in version 0.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
What
Synced skills now start their description with
[yoke], and the/prdescription is cut to one sentence. Skill names are unchanged, so a same-named skill of your own still wins.Why
yoke skills use generic names like
/pr, so when several skill sets are installed the description is the only way to tell them apart.How
The description is quoted in the frontmatter because an unquoted
[yoke]parses as a YAML list.