dependency-upgrade

Upgrade software dependencies with per-commit testing and vulnerability checks.

6|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/wesleyosantos91/multi-agents --skill dependency-upgrade-wesleyosantos91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-upgrade
Source: https://github.com/wesleyosantos91/multi-agents/tree/main/devin/.devin/skills/dependency-upgrade
Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill dependency-upgrade-wesleyosantos91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dependency upgrades can introduce breaking changes or leave known vulnerabilities unpatched, increasing outages and security risk.

Core Features & Use Cases

  • Structured upgrade workflow: inventory current versions, prioritize by vulnerability/EOL/major lag, and validate the target release (GA status, changelog, breaking changes, runtime compatibility).
  • Safe execution strategy: update one dependency per commit to isolate failures, run tests after each change, and fully migrate for major updates.
  • Ecosystem-specific commands: provides practical tooling guidance across Java (Maven), Python, Go, Node.js, and Terraform to find outdated packages and verify vulnerabilities.

Quick Start

Ask the AI to review and upgrade the project dependencies using one-change-per-commit steps while running the appropriate vulnerability checks for your stack.

Frequently Asked Questions about dependency-upgrade

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

FAQPage Schema
How do I safely upgrade project dependencies without introducing breaking changes?

To safely upgrade dependencies, inventory current versions, validate target GA releases, review changelogs for breaking changes, and update one dependency per commit with runtime compatibility checks and tests.

What's the best way to resolve critical and high CVEs across different programming ecosystems?

Resolving critical and high CVEs requires running ecosystem-specific vulnerability scanning commands across Java, Python, Go, Node.js, and Terraform, prioritizing updates by severity, and validating patches with per-commit testing.

How do I check for outdated packages and vulnerabilities in Maven, Python, Go, Node.js, and Terraform?

Checking outdated packages and vulnerabilities involves running ecosystem-appropriate audit and outdated-version commands for Maven, Python, Go, Node.js, and Terraform to identify major version lag and security issues.

Can I upgrade multiple dependencies at once or should I update them individually?

Upgrading dependencies individually is required, applying a one-change-per-commit strategy to isolate failures, run targeted tests after each change, and fully migrate major updates without introducing untraceable breakage.

When do I need to perform a full migration for a major framework version upgrade?

A full migration is needed for major dependency upgrades, requiring GA-version validation, changelog review for breaking changes, runtime compatibility checks, and per-commit testing to ensure framework stability.

Why do dependency upgrades cause outages and how can I prevent them?

Dependency upgrades cause outages when breaking changes go undetected, but you can prevent them by validating target release GA status, reviewing changelogs, checking runtime compatibility, and isolating updates per commit.