dependency-upgrader

jMerta's avatarfrom jMerta

Upgrade dependencies for Java/Kotlin (Gradle/Maven) and TypeScript/Node projects with minimal risk: plan the bump, apply changes incrementally, run tests/builds, and document breaking changes. Use when the user asks to bump deps, update frameworks, or address CVEs.

⭐90stars🔀6forks📁View on GitHub🕐Updated Jan 2, 2026⬇️2downloads

When & Why to Use This Skill

The Dependency Upgrader is a specialized Claude skill designed to automate and streamline the process of updating software dependencies in Java, Kotlin, and TypeScript projects. It minimizes technical debt and security risks by planning incremental updates, verifying changes through automated builds and tests, and providing detailed documentation of breaking changes and migration paths. By integrating with package managers like Maven, Gradle, and npm, it ensures that your project remains secure, stable, and up-to-date with minimal manual intervention.

Use Cases

  • 1. Security Vulnerability Remediation: Quickly address CVEs by identifying and upgrading vulnerable libraries to their latest secure versions while ensuring project stability through automated verification.
  • 2. Major Framework Migrations: Manage high-risk upgrades, such as moving to a new major version of Spring Boot or Node.js, by analyzing migration guides and applying changes incrementally to catch breaking changes early.
  • 3. Routine Maintenance and Tech Debt Reduction: Automate the periodic bumping of minor and patch versions across complex monorepos or multi-module projects to stay current with the ecosystem and avoid version rot.
  • 4. Automated Build & Test Validation: Ensure every dependency change is safe by automatically executing the project's specific test suites and build commands (e.g., ./gradlew build or npm test) after each update step.
namedependency-upgrader
description"Upgrade dependencies for Java/Kotlin (Gradle/Maven) and TypeScript/Node projects with minimal risk: plan the bump, apply changes incrementally, run tests/builds, and document breaking changes. Use when the user asks to bump deps, update frameworks, or address CVEs."

Dependency upgrader

Goal

Safely upgrade dependencies with minimal, reviewable diffs and clear verification.

Inputs to ask for (if missing)

  • Which ecosystem: Gradle/Maven, Node/TypeScript, or both.
  • Scope: one dependency, a set (e.g., Spring Boot), or "everything".
  • Constraints: patch/minor only vs allow majors; time budget; CI requirements.
  • Motivation: CVE fix, feature need, or routine maintenance.
  • Can the agent use web search to confirm latest versions and read migration notes? (If not, rely on registry lookups.)

Workflow (checklist)

  1. Detect the project type and package manager
    • Node: package.json + lock file (pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lock).
    • Gradle: gradlew, build.gradle(.kts), settings.gradle(.kts), gradle/libs.versions.toml.
    • Maven: pom.xml.
    • If the required package manager or build tool is missing (npm/pnpm/yarn/bun, Gradle, Maven), tell the user and ask whether to install it or proceed with a manual edit-only upgrade.
  2. Establish a baseline
    • Record current versions (dependency file + lock files).
    • Run the smallest reliable test/build command the repo uses (then expand if needed).
  3. Plan the upgrade
    • Prefer the smallest bump that solves the problem.
    • Choose target versions using up-to-date sources:
      • Use web search (if available) to confirm latest stable versions and skim official release notes/migration guides.
      • Cross-check with the registry/source of truth (npm registry, Maven Central, Gradle Plugin Portal).
    • Group by risk:
      • low: patches/minors, leaf deps
      • medium: build tools/plugins
      • high: framework majors (Spring Boot), runtime bumps (Java/Node)
    • For majors: skim upstream migration notes and list expected breakpoints before editing.
  4. Apply upgrades incrementally
    • Update one group at a time; keep diffs focused.
    • After each group: run tests/build and fix breakages immediately.
    • Use the playbooks in references/ for ecosystem-specific commands.
  5. Validate and document
    • Run the repo's "CI equivalent" commands (tests + build).
    • Document:
      • what changed (versions)
      • why (CVE, compatibility, feature)
      • notable migrations or breaking changes
      • any follow-ups (deprecations, future majors)

Deliverable

Provide:

  • The list of version bumps (old -> new).
  • The commands run and their result (tests/build).
  • Any breaking changes and required code/config migrations.