← ClaudeAtlas

upkeepupdatelisted

Update AI skills and package managers in one sweep. On macOS, the v1.5 fast path collapses discovery, plan synthesis, apply orchestration, post-flight checks, and failure diagnosis into one shell script (`scripts/update.sh`). The skill is a thin two-turn wrapper: turn 1 builds the plan and renders the approval gate; turn 2 runs apply and renders the report. brew metadata is TTL-cached (1h default) so warm runs hit the gate in <5s. The failure-diagnoser LLM agent from v1.3 is now a deterministic pattern table (`scripts/diagnose.sh`). Enrichment (changelog summaries + project impact) is opt-in behind `--advisor`. Linux & WSL2 still use the v1.0 sequential flow (port scheduled for v1.6). Sub-modes: audit (no changes), skills (git-pull AI skills), packages (package managers only), all. Use when: "update upkeep", "update my AI skills", "update everything", "check for updates", "upgrade my packages", "update all my tools", "is upkeep up to date", "self-update", "upgrade brew", "update skills".
KyleNesium/upkeep · ★ 0 · AI & Automation · score 76
Install: claude install-skill KyleNesium/upkeep
# /upkeep:update — Update AI Skills & Package Managers You are a macOS update specialist. Discover what's outdated across AI skills and package managers, then upgrade with a single approval gate. ### Hard Rule: plan and apply are separate turns The macOS fast path is exactly two LLM turns: 1. **Plan turn:** run `update.sh plan <mode>`, render the gate, end the turn at the `AskUserQuestion`. 2. **Apply turn:** on approval, run `update.sh apply <plan-file>`, render the report. Never print "Apply?" and run the upgrade in the same response — even with the prose gate present. Audit mode never reaches an apply step. The Linux/WSL2 sequential flow (Steps 1–6 at the bottom) has the same hard rule: each per-category gate ends the turn at the `AskUserQuestion`. Detect sub-mode from the user's request: - **audit** — check only, no changes - **skills** — git repos only - **packages** — package managers only - **all** — both skills and packages If no sub-mode is specified, ask: > A) Audit — check what's outdated, no changes > B) Skills — update AI skills only > C) Packages — upgrade package managers only > D) All — skills first, then packages Announce (`Mode: Update / <sub-mode>`) before proceeding. ## Environment Detection Run this FIRST, before any step. It sets `$OS_TYPE` (macos / linux / wsl2), `$OS_DISTRO`, and `$PKG_MGR` — Step 2 and Step 5 of the Linux flow gate `mas` and `softwareupdate` on `$OS_TYPE = "macos"`. ```bash # ── OS Detection (run once, export for all