update-aegis

Files (1)

• SKILL.md

SKILL.md (first lines)

# Update Aegis

Update the installed Aegis Method Pack for the current AI coding host.

This skill is host maintenance. Do not edit the target project just because the
user asked to update Aegis.

## Default Semantics

- `aegis:update` updates the current host's registered Aegis installation.
- Updating every registered host requires an explicit `--all` request.
- If more than one host is registered and the current host cannot be identified,
  ask one concrete question before updating.
- Do not update a development checkout when the installed method-pack root is a
  separate path.
- Do not perform background automatic updates. The local registry may record
  `updateMode`, but this skill only performs explicit user-triggered updates.

## Evidence First

From the installed method-pack root, inspect the host-scoped registry:

```bash
python scripts/aegis-update.py status --json
```

If the registry is missing, register the current host before updating. Use the
host's install guide and actual discovery path rather than guessing.

If `~/.config/aegis/config.toml` already declares `method_pack_root`, prefer
that canonical root when registering additional hosts. Host-specific discovery
paths, copied skill directories, plugin caches, or adapter payloads should be
treated as generated / host-managed views into the same Aegis body, not as
separate editable checkouts.

Codex example:

```bash
python scripts/aegis-update.py register \
  --host codex \
  --sync-mode junction \
  --discovery-root ~/.agents/skills/aegis \
  --reload-hint "restart Codex"
```

Copy-based host example:

```bash
python scripts/aegis-update.py register \
  --host codebuddy \
  --sync-mode copy-skills \
  --discovery-root ~/.codebuddy/skills \
  --reload-hint "restart CodeBuddy"
```

Copy synchronization uses the installation registry's scoped file inventory.
It preserves unrelated files and local edits, and stops on conflicting writes
before changing the view. An identical legacy copy can be adopted; a differing
copy needs reconciliation or a separate discovery root. Unknown stale copies
are retained. Names and prefixes alone never prove ownership; do not delete
them to make verification pass.
Source names that collide under Unicode normalization/case folding are rejected
for portability. A case-only rename with changed contents can require moving
the conflicting file to a backup outside the discovery root, or selecting a
separate root. Preserve existing files during reconciliation.

Prefixed direct-child host example:

```bash
python scripts/aegis-update.py register \
  --host copilot \
  --sync-mode junction \
  --discovery-shape direct-child \
  --discovery-root <target-repo>/.github/skills \
  --discovery-name-prefix aegis- \
  --reload-hint "restart Copilot session or reopen the repository"
```

Kimi Code CLI automatic installations are plugin-managed. Do not use the Aegis
updater against Kimi's managed plugin copy. In Kimi, run the native update or
reinstall flow, verify the selected managed plugin, then reload:

```text
/plugins install https://github.com/GanyuanRan/Aegis
/plugins info aegis
/reload
```

If Kimi requires confirmation or removal before replacing the managed copy,
follow its exact plugin-manager prompt. Then locate the managed root from
`/plugins info aegis` and run:

```bash
cd <aegis-method-pack-root>
python scripts/aegis-doctor.py --json --host-profile kimi-code-auto
```

Kimi Code CLI **Explicit Compatibility Installation** example:

```bash
python scripts/aegis-update.py register \
  --host kimi-code \
  --sync-mode junction \
  --reload-hint "restart Kimi Code CLI"
```

When `--discovery-root` is omitted for `kimi`, `kimi-code`, or
`kimi-code-cli`, the updater uses `$KIMI_CODE_HOME/skills` or, when
`KIMI_CODE_HOME` is unset, `~/.kimi-code/skills`. Use this updater path only
when the Aegis Kimi plugin is disabled or uninstalled and the user has selected
explicit compatibility mode.

Plugin-managed hosts can be registered, but the updater reports that the host
plugin manager owns the update path:

```bash
python scripts/aegis-update.py register \
  --host opencode \
  --sync-mode plugin-managed \

From GanyuanRan/Aegis, MIT.

More from GanyuanRan/Aegis