update-dependencies · git:20260927.67acf2e · 2026-09-27 · sha256 af4fdec61adf74e6

update-dependencies git:20260927.67acf2eA

Immutable. This exact content never changes and is served at /api/v1/blob/af4fdec61adf74e6.

---
name: update-dependencies
description: Survey and update this WongStack source repo's toolchain and app dependencies on demand, check the OpenSpec CLI contract, and hand changes to /save. Use only when asked to update dependencies.
user-invocable: true
---

# /update-dependencies

This meta-repo-only skill is absent from [the payload inventory](../wong-sync/references/payload-files.json), so no target gets it, and editing only it is no payload release. It runs on demand for this repo, never by schedule.

## Survey and update

Report installed (`--version`) and latest versions of `openspec`, `agent-browser`, `gh`, `git`, `node`, and each `app/package.json` dependency. Act on `npm outdated`'s Latest in `app/`, majors included; its nonzero exit is normal. If all is current, say so and stop without `/save`.

Update machine tools normally, asking first per [required tools](../../../wiki/development/required-tools.md) when that needs sudo or changes the runtime more than the user expects. Apply each major's migration notes; update `app/package-lock.json` with `app/package.json`.

## Check the OpenSpec contract

After a CLI update, check `init --tools none`, `context`, `status --json`, artifact/apply/archive instructions, validation, and archive flags against a disposable fixture, the release notes, and [the shared contract](../plan/references/openspec-cli.md). [No generated layer](../plan/references/openspec-cli.md) exists: never run `openspec update` or regenerate or patch `openspec-*` skills. Report a changed CLI field and adapt the owning WongStack skill before saving; never silently accept a missing contract.

If payload files changed, follow [the release rule](../../rules/payload.md); otherwise say why no release is due.

## Hand off

Pass a nonempty diff to `/save`; [the change loop](../../../wiki/development/the-change-loop.md#the-gate) owns git and the gate. Never claim green CI proves every major safe. Report each stage: current surfaces, migrations, CLI contract evidence, and the checks CI ran.