upgrade

Re-applies user MOD.md deltas onto fresh upstream capability renders with diff-gated commits.

3|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/AlmogBaku/aos --skill upgrade-almogbaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upgrade
Source: https://github.com/AlmogBaku/aos/tree/main/capabilities/capability-lifecycle/skills/upgrade
Command: npx skills add https://github.com/AlmogBaku/aos --skill upgrade-almogbaku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Upgrading installed aos capabilities risks losing the user's hand-edits and personalization, and blind re-renders can silently destroy untracked files or leave stale tool binaries behind. ## Core Features & Use Cases - Personalization preservation: Folds the user's hand-edited render drift into MOD.md before re-applying it to fresh upstream, so upgrades never erase customization. - Diff-gated commits: Stages each capability's re-render in the personal git repo and requires review of the staged diff before committing, with a clean restore path on decline. - Lifecycle housekeeping: Repairs broken links, re-installs shipped CLI tools via uv, handles renamed skills and absorbed capabilities, and offers retirement of MOD statements now covered upstream. - Use Case: After pulling the latest aos upstream clone, ask your agent to upgrade all installed capabilities; it re-renders each one against your MOD.md, shows you a per-capability diff, and commits only what you approve. ## Quick Start Tell your agent to upgrade my installed aos capabilities after pulling the latest upstream, and review each staged diff before it commits.

Frequently Asked Questions about upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade installed aos capabilities after a git pull?▼

Run the upgrade flow after pulling the upstream clone: it detects capabilities whose manifest version differs from the lockfile, re-renders each against your MOD.md, and presents a staged git diff per capability for approval before committing.

Will upgrading an aos capability lose my customizations?▼

No. Hand-edits detected by aos-cap verify are folded into MOD.md first, then MOD.md is re-applied to fresh upstream, so your personalization survives the upgrade. The current install is treated as a drift source, never a merge input.

What is the difference between capability upgrade and capability evolve?▼

Upgrade preserves existing personalization by re-applying MOD.md to new upstream versions, while evolve changes what a capability does for you. Use upgrade after upstream releases; use evolve when you want new behavior.

Why does the upgrade check for untracked files before re-rendering?▼

The --force re-render deletes and recopies the render directory, so an untracked file would be destroyed with no commit to recover it from. The skill names any untracked entries and asks for a decision before proceeding.

What happens when a capability no longer exists upstream?▼

It was absorbed into another capability. The skill unlinks its skill links, removes the lockfile entry, and lets the absorbing capability's own upgrade render the replacements, retiring stale context-block markers in the same pass.