← ClaudeAtlas

dependency-upgradelisted

Upgrade dependencies, runtimes and base images in any ecosystem, one major at a time or as a batch of minor and patch updates, each step tested and committed. Use when the user says 'upgrade dependencies', 'bump packages', 'upgrade to React 19', 'bump the Go version', 'update the base image', or when versions are far behind, Dependabot has many PRs open, or the user asks what an upgrade breaks.
paureis/pau-skills · ★ 2 · AI & Automation · score 71
Install: claude install-skill paureis/pau-skills
# Dependency upgrade Upgrade dependencies so that every step can be judged, bisected and rolled back. The method is the same in every ecosystem; only the commands change, and those are in the reference files. Request from the user: $ARGUMENTS Reference files, read when you reach their phase: - `${CLAUDE_SKILL_DIR}/ECOSYSTEMS.md`: per-ecosystem commands (list outdated, upgrade one package, move to a new major, regenerate the lockfile, audit, explain why a package is present, where changelogs live), plus runtimes, toolchains and Docker images. - `${CLAUDE_SKILL_DIR}/RESEARCH.md`: the checklist for researching one major bump. If you started this skill on your own, without the user typing its name or asking for what it does, first say in one or two lines what it will do and what it will cost, and wait for a yes. A remark or a question that only matches its description is not asking for it. If the user asked for it, or the brief you are working from does, go ahead. ## Pick the mode - **Major mode**: one key package or framework moves across a major version (or a runtime moves to a new major). Phases 1 to 7 in full, with phase 3 done carefully for that package and for everything it drags along. - **Hygiene mode**: a batch of minor and patch updates. Phase 3 is light (skim release notes for anything marked breaking or deprecated, because semver is a promise, not a guarantee). Any major that shows up in the inventory is listed and deferred to its own major-mode run un