Migrate legacy skills manifests on first read - #24
Closed
git-hulk wants to merge 1 commit into
Closed
Conversation
git-hulk
force-pushed
the
skills-legacy-migration
branch
from
August 31, 2026 13:50
5e2ceda to
7996a17
Compare
Convert the pre-versioning manifest (top-level skills/sources fields) to the repository-keyed format automatically the first time it is read. The migrator groups legacy skills by canonical repository and locks each one to the HEAD commit of its existing ~/.clime/sources checkout rather than pulling the remote, because the remote's current HEAD cannot prove which content was installed locally. That checkout is snapshotted into the immutable cache, so the migrated state syncs offline. The migrated manifest, cached content, catalogs, and conflicts are validated before the original file — preserved as skills.yaml.bak — is replaced by rename. A local directory source, a missing checkout, an unresolvable HEAD, or a post-migration name conflict aborts the whole migration, leaving the legacy manifest and agent targets unchanged with an error that directs the user to move local content to a Git repository or resolve the conflict. The legacy mutable source cache is not deleted; a later clime skills purge removes unreferenced data. Assistant By Fable 5 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
git-hulk
force-pushed
the
skills-legacy-migration
branch
from
September 1, 2026 02:18
7996a17 to
7f36799
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.
Convert the pre-versioning manifest (top-level skills/sources fields)
to the repository-keyed format automatically the first time it is
read.
The migrator groups legacy skills by canonical repository and locks
each one to the HEAD commit of its existing ~/.clime/sources checkout
rather than pulling the remote, because the remote's current HEAD
cannot prove which content was installed locally. That checkout is
snapshotted into the immutable cache, so the migrated state syncs
offline. The migrated manifest, cached content, catalogs, and
conflicts are validated before the original file — preserved as
skills.yaml.bak — is replaced by rename.
A local directory source, a missing checkout, an unresolvable HEAD, or
a post-migration name conflict aborts the whole migration, leaving the
legacy manifest and agent targets unchanged with an error that directs
the user to move local content to a Git repository or resolve the
conflict. The legacy mutable source cache is not deleted; a later
clime skills purge removes unreferenced data.
🤖 Generated with Claude Code