dep-upgrade

Upgrade dependencies one at a time with test verification and git rollback.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Projects accumulate outdated or vulnerable dependencies across multiple ecosystems, and upgrading them in bulk risks breaking builds and obscuring which change caused failures. This Skill provides a safe, systematic way to audit, prioritize, and apply dependency upgrades while ensuring test verification and immediate rollback on failure so maintainers can remediate vulnerabilities without destabilizing the codebase.

Core Features & Use Cases

  • Cross-ecosystem detection: Automatically detects Go, Node.js, Python, Rust, and .NET projects from manifest files and treats each ecosystem separately.
  • Audit and prioritization: Combines outdated-package listings with vulnerability scanners to produce a prioritized upgrade plan (CRITICAL → LOW).
  • One-at-a-time execution with safety: Upgrades packages individually, runs tests after each change, updates lockfiles, and rolls back via git if tests fail; never auto-commits or creates branches.
  • Use case: Resolve a security alert by auditing the repo, presenting a prioritized plan for approval, and safely applying fixes while preserving a clear audit trail.

Quick Start

Use the dep-upgrade skill to audit dependencies, present a prioritized upgrade plan, and then upgrade approved packages one at a time with tests and rollback on failures.

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 outdated dependencies without breaking my build?

Safe dependency upgrades require applying changes one package at a time, running tests after each modification, and automatically restoring files from git on failure to prevent breaking the build.

How do I fix security advisories by prioritizing vulnerable package upgrades?

Fix security advisories by auditing outdated packages alongside vulnerability scanners to generate a prioritized upgrade plan, applying fixes from CRITICAL to LOW severity individually with test verification.

Does automated dependency upgrade work with Go, Node.js, Python, Rust, and .NET projects?

Automated dependency upgrade supports Go, Node.js, Python, Rust, and .NET projects by detecting ecosystem manifest files and executing ecosystem-specific upgrade and verification commands for each.

What is the best way to roll back a failed dependency upgrade in git?

The best way to roll back a failed dependency upgrade is restoring modified manifest and lockfiles from git immediately after test verification fails, preserving a clear audit trail without auto-committing.

How to audit outdated packages across multiple ecosystems systematically?

Audit outdated packages across multiple ecosystems by detecting project manifests, combining outdated-package listings with vulnerability scanner results, and presenting a prioritized plan for approval before execution.

Why does bulk upgrading dependencies risk obscuring failure causes?

Bulk upgrading dependencies risks obscuring failure causes because multiple simultaneous package changes make it difficult to isolate which specific upgrade introduced a test failure or build break.