skills.rest
alivecontext
alivecontextOFFICIAL
Explore all skills by this author →
WebsiteGitHub

alive:system-upgrade

Migrate ALIVE Context Systems from legacy formats to v3 structure.

124|7|Updated Feb 19, 2026
Search Tags:#automation#verification#migration#backup#kernel#upgrade#alive
One-click install
npx skills add https://github.com/alivecontext/alive --skill alive-system-upgrade
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: alive:system-upgrade
Source: https://github.com/alivecontext/alive/tree/main/plugins/alive/skills/system-upgrade
Command: npx skills add https://github.com/alivecontext/alive --skill alive-system-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ALIVE Context System upgrades require coordinated migration of legacy structures, safe renames, and state conversions with rollback capabilities to preserve integrity during major version jumps.

Core Features & Use Cases

  • End-to-end upgrade orchestration across v1->v3 and v2->v3, including backup, kernel renames, bundle flattening, manifest conversion, task migration, and state regeneration.
  • Automated discovery of legacy patterns, compatibility checks, and safe fallback paths with human-in-the-loop approvals.
  • Post-upgrade verification and rollback options in case of failure, with detailed logging and change tracking.

Quick Start

To begin, issue the upgrade command for the target world and follow the interactive prompts to review changes before execution.

Frequently Asked Questions about alive:system-upgrade

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

FAQPage Schema
How do I safely migrate an ALIVE Context System to the v3 structure?▼

To safely migrate an ALIVE Context System to v3, use the upgrade orchestration tool to handle kernel renames, bundle flattening, and manifest conversion. It supports v1 and v2 paths while generating backups across walnuts.

What is the best way to upgrade legacy ALIVE bundles without losing state?▼

Upgrading legacy ALIVE bundles without losing state requires automated state regeneration and manifest conversion. The system enforces backup generation and verification steps before applying changes to preserve data integrity.

Can I test an ALIVE system migration before committing to the changes?▼

You can test an ALIVE system migration using the optional dry-run mode. This allows you to review the generated Python upgrade script and verify compatibility checks before executing actual changes.

Does the ALIVE upgrade process support rollback after a failed kernel migration?▼

The ALIVE upgrade process includes post-upgrade verification and rollback options in case of failure. Safe fallback paths with human-in-the-loop approvals are enforced to manage kernel renames safely.

How does state regeneration work during a v2 to v3 ALIVE migration?▼

State regeneration during a v2 to v3 ALIVE migration works by converting legacy structures into the current format while preserving task data. The system discovers legacy patterns and applies coordinated conversions across walnuts.

Related Skills

Explore More Software Engineering Skills→
alivecontextalivecontext
124

alive:create-walnut

Scaffold ALIVE walnut folders with _kernel files from SKILL.md frontmatter.

Official
Advanced
deveshkumarsdeveshkumars

gstack-upgrade

Detect gstack install type and apply the appropriate upgrade path.

Community
Advanced
chrislyonschrislyons

dependency.audit

Audit npm, Python, and Rust dependencies for vulnerabilities, licenses, and upgrades.

Community
Intermediate
Largo2z9Largo2z9
1

update-workspace

Update PhantomOS workspaces to newer releases while preserving operator data.

Community
Advanced