feat: support portable producer skill roots#22
Merged
Conversation
Member
Author
|
Final validation report:
|
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.
Opened on behalf of Onur Solmaz (
osolmaz).Summary
Producer CLIs could only use
findSkillsRoot()when their bundled skills lived underskills/.This change makes
.agents/skills/a first-class producer layout too.It keeps the old
skills/behavior, adds multi-root support, and documents the portable layout.What Changed
Skill discovery now understands both conventional package skills and portable repo-local agent skills.
Existing callers that use
skills/keep working unchanged.findSkillsRoots()for CLIs that intentionally ship more than one root.findSkillsRoot()preferskills/and fall back to.agents/skills/.handleSkillflag()andmaybeHandleSkillflag()to receive one root or an array of roots..agents/skillsdiscovery and multi-root listing.Testing
I ran the package gates and the new tests pass.
npm run formatnpm run buildnpm run lintnpm run format:checknpm testRisks
The compatibility risk is low because
skills/remains the preferred root and the publicskillsRootoption still accepts the original URL/string inputs.The only behavior change is that a missing
skills/directory can now resolve to.agents/skills/instead of throwing.