Reuse Foundation shared sources while preserving legacy skill edits - #83
Merged
Merged
Conversation
This was referenced Oct 1, 2026
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.
Remote skills and bundles can resolve the same repository into separate caches. Reuse Foundation's optional immutable source store so an adopted exact repository/commit has one shared source object.
Existing skill copies and local edits remain authoritative until safe staging adoption. Bare Git URLs keep the Skills default main ref. Without the compatible Foundation API, the legacy resolver continues to work.
Depends on microsoft/amplifier-foundation#415 for shared-store opt-in; staggered upgrades remain supported. Recommended merge order: Foundation, Skills, Unified.
Validation: all 12 focused skill-source tests passed with the Foundation branch API, including shared bundle/skill reuse, default-ref behavior, legacy edit protection and absent-API compatibility. No live-service migration was performed.
Related consumer PR: microsoft/amplifier-unified#315.
Add generic
tool-skills.config.cache_dirfor hosts that share settings andlocal skills but own remote downloads. Both startup and on-demand resolution
honor it; omitted configuration retains CLI defaults. Explicit paths remain
authoritative. Follow-up source/cache coverage: 38 tests passed; additional
mount, hook and multi-source coverage: 35 passed.