Merge SLICC workspace file edits during platform version upgrades.
npx skills add https://github.com/ai-ecoverse/slicc --skill upgrade-ai-ecoverse
Please help me install this Agent Skill. Skill: upgrade Source: https://github.com/ai-ecoverse/slicc/tree/main/packages/vfs-root/workspace/skills/upgrade Command: npx skills add https://github.com/ai-ecoverse/slicc --skill upgrade-ai-ecoverse
This Skill eliminates the risk of losing custom user edits to SLICC workspace files (skills, sprinkles, and bundled scripts) when the platform upgrades to a new version, removing the need for manual reconciliation of changes after an update.
Ask the agent to use the upgrade skill to review the pending SLICC version changelog and confirm the workspace file merge if the changes look safe.
High-intent search queries and answers about installing and using this skill.
To upgrade without losing custom workspace edits, you need a safe three-way merge process that automatically reconciles upstream platform changes with your local file modifications. This preserves your custom skills and scripts while applying new version updates seamlessly.
A three-way merge for version updates is a process that compares the original base file, your local custom edits, and the new upstream release to safely combine changes. It is needed when a platform upgrade triggers and your local workspace files have been modified.
You can review a changelog before applying a version update by fetching and summarizing GitHub release commits. This presents the upcoming changes for your review, allowing you to confirm or dismiss the workspace file merge via a binary action card.
No, the SLICC upgrade process does not automatically overwrite custom skills. It uses a user-controlled workflow with no auto-applied changes, ensuring that upstream improvements are merged with your edits only after explicit manual confirmation.
If there are merge conflicts during a workspace sync, the process surfaces these conflicts for manual user resolution. This ensures safe, controlled updates by preventing automatic overwrites and requiring you to resolve conflicting changes in your skills, sprinkles, or scripts.
Yes, you can use this merge process for bundled scripts and sprinkles. It performs three-way merges across all SLICC workspace files, preserving your custom modifications to skills, sprinkles, and scripts during platform version upgrades.
ether-moonAutomates semantic versioning and changelog updates for the knowledge-distillery plugin.
gesmith0606Reapplies local patches to a new GSD version via three-way merge.
ai-ecoverseShowcase an interactive SLICC demo visualization with 12 concept cards.
chiptoe-svgExtract NanoClaw fork customizations into a migration guide for clean upstream upgrades.
