dependency-upgrader

Upgrade Java/Kotlin and TypeScript/Node dependencies with incremental tests and builds.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Nymbo/Skills --skill dependency-upgrader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-upgrader
Source: https://github.com/Nymbo/Skills/tree/main/dependency-upgrader
Command: npx skills add https://github.com/Nymbo/Skills --skill dependency-upgrader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Upgrades 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.

Core Features & Use Cases

  • Plan & scope: Decide bump scope and risk grouping (patch/minor/major).
  • Incremental upgrades: Update dependencies group-by-group with tests after each.
  • Documentation: Note breaking changes and migration steps.

Quick Start

Propose upgrading a dependency set, run tests, and document any breaking changes for the next PR.

Frequently Asked Questions about dependency-upgrader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade dependencies safely across my Maven or Gradle project?

Upgrade dependencies safely by planning the bump scope, applying changes incrementally group-by-group, running tests after each update, and documenting breaking changes. This minimizes risk by validating each step before proceeding to the next dependency.

Can I upgrade all dependencies at once or should I do them one at a time?

Group upgrades by risk level—patch, minor, or major—and apply them incrementally with tests between each group. Upgrading all at once obscures which change breaks your build; grouping isolates problems and keeps diffs minimal.

What's the best way to handle breaking changes when upgrading dependencies?

Document breaking changes and migration steps as you discover them during incremental upgrades. This surfaces what needs to change in your code before you commit, reducing surprise failures in production.

Does this work with both Java and Node.js projects?

Yes. Upgrade dependencies across Gradle, Maven, and Node ecosystems with the same minimal-risk approach: plan, apply incrementally, validate with tests and builds, and document changes.

How do I know which version to upgrade to?

The Skill selects target versions from up-to-date sources, baseline your current versions, and group candidates by semantic versioning bump type so you can choose scope—patch fixes only, minor features, or major upgrades.