package-updater-updatelisted

# Update packages Bring the repositories in scope up to date — one researched commit per toolchain pin and per named package, a bulk refresh for the rest, and each follow-up as its own commit. Use the `package-updater-updating-packages` skill for the phase structure. It reads the same references this command does, so the sweep and the single-package path cannot drift: `references/repo-scope.md`, `references/ecosystems.md`, `references/commit-conventions.md`, `references/upstream-links.md`, and `references/follow-ups.md`. For one named package, use the `package-updater-update-package` skill. For `.tool-versions`, `.nvmrc`, `packageManager` or `engines`, use the `package-updater-update-toolchain` skill. User arguments: $ARGUMENTS ## Context Repository — run this command and read the output: ```bash git remote get-url origin 2>/dev/null || echo "(not a git repository)" ``` Default branch — run this command and read the output: ```bash git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo "(unknown)" ``` Manifests, lockfiles and toolchain pins here — run this command and read the output: ```bash out=$(git ls-files -- 'pyproject.toml' '**/pyproject.toml' 'uv.lock' '**/uv.lock' 'poetry.lock' 'requirements*.txt' 'package.json' '**/package.json' 'pnpm-lock.yaml' 'package-lock.json' 'yarn.lock' 'Cargo.toml' 'Cargo.lock' 'go.mod' '.tool-versions' '.nvmrc' '.python-version' 'mise.toml' '.mise.toml' 2>/dev/null | grep -v node_modules | head -40); if [ -n "$out"