dep-upgrade

Upgrade dependencies sequentially with test verification and rollback on failure.

3|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/rshade/agent-skills --skill dep-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dep-upgrade
Source: https://github.com/rshade/agent-skills/tree/main/skills/dep-upgrade
Command: npx skills add https://github.com/rshade/agent-skills --skill dep-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Safe systematic dependency upgrade with vulnerability scanning and rollback capability. Detects project ecosystem, audits outdated and vulnerable packages, presents a prioritized upgrade plan, and executes upgrades one at a time with test verification after each. Use when updating dependencies, fixing vulnerability alerts, or performing periodic dependency maintenance.

Core Features & Use Cases

  • Detects project ecosystem by scanning for package manager files: go.mod, package.json, pyproject.toml, Cargo.toml, *.csproj
  • Audits outdated and vulnerable packages across ecosystems and presents a prioritized upgrade plan
  • Executes upgrades one at a time with test verification after each, with rollback on failure
  • Never auto-commit; supports multi-ecosystem upgrades and per-ecosystem workflows

Quick Start

Initiate a guided, one-at-a-time dependency upgrade workflow with test verification after each upgrade.

Frequently Asked Questions about dep-upgrade

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

FAQPage Schema
How do I safely upgrade dependencies one at a time with rollback?

Safe dependency upgrades are executed sequentially per package with automated test verification after each update, triggering a rollback on failure to keep the project stable. It detects ecosystems like Go and Node.js automatically.

Can I upgrade vulnerable packages across multiple ecosystems in one project?

Multi-ecosystem dependency upgrades are supported by scanning for package manager files like go.mod, package.json, pyproject.toml, Cargo.toml, and *.csproj. It audits outdated and vulnerable packages across ecosystems and presents a prioritized upgrade plan.

What's the best way to fix vulnerability alerts without breaking my build?

Fixing vulnerability alerts safely requires auditing vulnerable packages and applying upgrades one at a time with test verification. If a test fails, the tool rolls back the upgrade to prevent breaking your build.

Does the dependency upgrade process auto-commit changes to my repository?

The dependency upgrade process never auto-commits changes to your repository. It applies lockfile updates and per-package upgrades sequentially, leaving the final commit decision to the developer.

How do I start a guided dependency maintenance workflow?

A guided dependency maintenance workflow starts by detecting your project ecosystem and auditing outdated packages. It then executes upgrades one at a time, verifying tests after each step and rolling back on failure.

What happens if a test fails during a dependency upgrade?

If a test fails during a dependency upgrade, an automatic rollback is triggered for that specific package. This safeguard ensures that a broken upgrade does not affect the rest of your sequential dependency updates.