feat(cli): harden per-registry skill updates - #173
Closed
codeaholicguy wants to merge 4 commits into
Closed
Conversation
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.
Summary
The optional per-registry
skill updatecapability and exactowner/repofiltering already existed on main. This hardening follow-up adds directSkillRegistrycontract coverage and improves the selector UX without reimplementing the baseline.NotFoundErrormessagesValidation
npm cinpm run build— 6/6 projectsnpm run lint— 6/6 projects, warnings onlynpm test— 1,923 tests across 137 filesSkillRegistry.test.ts— 9/9 testsSkillRegistry.ts, including unrelated fetch/clone paths; all added selector branches exercisednpx ai-devkit@latest lint --feature skill-update-registry[registry-id]Risks
None known. No public API, schema, cache layout, or command parser changes.