aios-update

Synchronize installed AI-OS files with plugin updates using staged diffs and rollback.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/ludwigawra/florentxlundaisociety --skill aios-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aios-update
Source: https://github.com/ludwigawra/florentxlundaisociety/tree/main/plugin/skills/aios-update
Command: npx skills add https://github.com/ludwigawra/florentxlundaisociety --skill aios-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a safe, non-destructive way to synchronize an installed AI-OS with the current plugin version, ensuring users receive new skills, hooks, and template improvements without losing or overwriting their personal brain data.

Core Features & Use Cases

  • Non-destructive synchronization: Detects added, updated, unchanged, and removed skills, hooks, templates, and settings while never modifying user brain folders like HIPPOCAMPUS or MEMORY.md.
  • Conflict resolution and safety checks: Prompts on user-modified files, preserves user copies, performs syntax-checking for shell hooks, stages changes, and supports full rollback on failure.
  • Use Case: After running npm update @aios/plugin, preview a dry-run diff to see exactly what will change in .claude/ and then apply only the approved updates so the user's customizations remain intact.

Quick Start

Invoke the aios-update skill to diff the plugin against your installed AI-OS and then apply selected changes after reviewing conflicts.

Frequently Asked Questions about aios-update

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

FAQPage Schema
How do I update AI-OS plugin skills without overwriting custom brain folders?

Non-destructive synchronization detects added, changed, and removed plugin files while strictly protecting user-owned brain folders like HIPPOCAMPUS and MEMORY.md from being overwritten.

How do I preview file changes before applying a plugin update?

Preview file changes by running a dry-run diff that compares the plugin tree against your installed .claude directory, showing exactly what will be added, updated, or removed before any modifications occur.

What happens to user-modified files during an AI-OS sync?

During an AI-OS sync, user-modified files trigger conflict resolution prompts, preserving your custom changes while staging the plugin's shipped updates for selective application.

Can I rollback a failed AI-OS plugin update?

Yes, updates are staged with rollback support, meaning if a failure occurs during synchronization or a shell syntax-check fails on hooks, the system reverts all changes to restore the previous state.

How do shell hooks get validated during a non-destructive update?

Shell hooks undergo strict syntax-checking during the update process to prevent broken scripts from being applied to your .claude directory, failing safely before any modifications are staged.

When do I need to run a non-destructive sync for AI-OS?

Run a non-destructive sync after updating the plugin package to reconcile new skills, hooks, templates, and settings with your local installation while ensuring shipped-hash tracking prevents silent overwrites.