From amplify
Safely upgrades Elixir Mix/Hex dependencies via patch/minor bumps, major migrations with changelog research, and post-update verification. Triggered by requests to update deps, bump packages, or run mix hex.outdated.
How this skill is triggered — by the user, by Claude, or both
Slash command
/amplify:update-depsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this workflow for Elixir projects that use Mix + Hex.
Use this workflow for Elixir projects that use Mix + Hex.
git status --short.
AskUserQuestion (single-select):
mix hex.info (no args). If Hex is not installed, run mix local.hex --force first.mix hex.outdated.mix.exs contains apps_path): note that version constraints may need updating in each apps/<app>/mix.exs. mix deps.update from the root works for all apps.mix deps.update <dep_name>mix deps.update --all is acceptable.mix.lock) is updated automatically by mix deps.update. Commit it together with any mix.exs changes.For each dependency with a major bump:
mix.exs. Use ~> X.0 (e.g., ~> 2.0) for most libraries. Only use >= X.0.0 and < Y.0.0 if the library explicitly recommends it in its upgrade guide.mix deps.update <dep_name> to apply the new constraint.mix hex.info <dep_name> to find package/repo links.https://hexdocs.pm/<dep_name> (look for changelog, migration, or upgrade sections).CHANGELOG*, release notes, and upgrade guides.If a major upgrade fails verification and cannot be resolved quickly:
git checkout mix.exs mix.lock).Run these commands after each update batch and after each major dependency:
mix compile --warnings-as-errors
mix format --check-formatted
mix test
If mix compile --warnings-as-errors fails due to pre-existing warnings unrelated to the upgrade, note them and rerun without --warnings-as-errors (mix compile) to confirm the upgrade itself is clean. Do not fix pre-existing warnings unless asked.
If the project defines additional CI checks, run the same checks used in .github/workflows.
Failure handling:
mix format.mix hex.outdated again and confirm the remaining items (if any) are intentional.npx claudepluginhub wunki/amplify --plugin ask-questions-if-underspecifiedPlans and executes safe, incremental dependency upgrades with risk assessment, migration guides, compatibility checks, and rollback strategies.
Coordinates safe dependency upgrades across multiple package managers (npm, pip, cargo, maven, gradle), handling lockfiles, version conflicts, vulnerability patches, and migration risk.
Runs dependency-upgrade campaigns: outdated scan, batch-by-severity bumps, breaking-change remediation, and lockfile audit. Use for CVE remediation, major upstream releases, or quarterly hygiene.