Add the repository-keyed versioned skills manifest - #27
Closed
git-hulk wants to merge 1 commit into
Closed
Conversation
Introduce the desired-state model of repository-versioned skill
management: ~/.clime/skills.yaml keyed by repository, each entry
locking a version (tag or full commit SHA) and the skills selected
from that repository. The legacy manifest remains in use by the CLI
until the switch lands.
- Mutations (SetVersion, AddSkills, AddRepo, RemoveSkill) edit YAML
nodes rather than remarshal structs, so user comments, entry
order, and key spelling survive round trips; skills insert in
sorted positions, and removing a repository's final skill removes
the entry.
- Keys normalize before lookup, so acme/agent-skills and
github.com/acme/agent-skills identify the same repository, while
the existing spelling is never rewritten.
- Validate checks the complete manifest and reports every problem
at once: alias duplicates, missing versions, empty or duplicate
skill selections, and skill names claimed by two repositories
(both agent targets install into <skills-root>/<skill-name>).
- Save writes through a temporary file and rename so a failed write
never truncates the previous manifest. A legacy-format file is
rejected with a clear error here; automatic migration lands at the
top of this stack.
Assistant By Fable 5
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
git-hulk
force-pushed
the
skills-versioned-manifest
branch
from
September 1, 2026 02:18
1263ab6 to
69fb907
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
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.
Introduce the desired-state model of repository-versioned skill
management: ~/.clime/skills.yaml keyed by repository, each entry
locking a version (tag or full commit SHA) and the skills selected
from that repository. The legacy manifest remains in use by the CLI
until the switch lands.
Mutations (SetVersion, AddSkills, AddRepo, RemoveSkill) edit YAML
nodes rather than remarshal structs, so user comments, entry
order, and key spelling survive round trips; skills insert in
sorted positions, and removing a repository's final skill removes
the entry.
Keys normalize before lookup, so acme/agent-skills and
github.com/acme/agent-skills identify the same repository, while
the existing spelling is never rewritten.
Validate checks the complete manifest and reports every problem
at once: alias duplicates, missing versions, empty or duplicate
skill selections, and skill names claimed by two repositories
(both agent targets install into /).
Save writes through a temporary file and rename so a failed write
never truncates the previous manifest. A legacy-format file is
rejected with a clear error here; automatic migration lands at the
top of this stack.
🤖 Generated with Claude Code