eg-upgradelisted

Upgrade a project that already runs on EstreGenesis — bring its seed up to the current release (Migration B numbered delta, additive only), refresh the installed EG plugins from the marketplace, and report what actually moved. Invoke when a new EG release lands, when the project's seed marker is behind, or via /egup. Requires .agent/seed_prompt.md with its version marker intact; a project without one goes to eg-bootstrap or eg-migration.
SoliEstre/EstreGenesis · ★ 8 · AI & Automation · score 78

Install: claude install-skill SoliEstre/EstreGenesis

# /eg-upgrade (`/egup`) — bring seed + plugins + skills up to date Mode **M2** (the seed's Migration B) plus the plugin/skill layer the seed does not cover. ## 0. Read the marker (this is the whole basis of the diff) Read `.agent/seed_prompt.md` and pull its header comment: ```  ``` - **No file** → not an upgrade: route to `/eg-bootstrap` (new) or `/eg-migration` (existing rules). Stop. - **File but no version marker** �� the seed was hand-edited or truncated. Say so, and offer a re-install of the same tier as the recovery path — do not guess a version. Record `(tier, language, from_version)`. ## 1. Compute the delta from the upstream changelog The changelog is the SSoT for what changed between releases (the seed files carry only a marker, deliberately): - `https://raw.githubusercontent.com/SoliEstre/EstreGenesis/main/CHANGELOG.md` Fetch it, find the current release, and collect every entry newer than `from_version`. Two axes move at different rates — keep them separate: - **Seed marker** (`v2.5.x` on the seed files) — bumps only when the seed *content* changes. Most releases do not touch it. - **Release version** (the repo's `vX.Y.Z`) — bumps every meaningful cut, including module-only cuts that do not affect the seed at all. If the seed marker did not move, say that plainly: the project's charter is already current and only the module/plugin layer needs attention. T