Verified:GitHub

dependency-upgrade

Plan and execute dependency upgrades with risk-based batching and verification.

1|Updated Jul 13, 2026

Search Tags:#release management #build verification #version bump #package maintenance #dependency upgrade #security fixes

Ready to run

npx skills add https://github.com/vh2224/forge-executor --skill dependency-upgrade-vh2224

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dependency-upgrade
Source: https://github.com/vh2224/forge-executor/tree/main/src/resources/skills/dependency-upgrade
Command: npx skills add https://github.com/vh2224/forge-executor --skill dependency-upgrade-vh2224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a messy set of outdated or vulnerable dependencies into a controlled upgrade plan that is easier to verify, safer to ship, and simpler to debug when something breaks.

Core Features & Use Cases

Risk-based batching: Separates dev dependencies, runtime patches, runtime minors, and majors so the safest upgrades land first.
Verification after every batch: Requires build, test, lint, and smoke checks between upgrade groups to catch regressions early.
Breakage handling: Isolates major-version migrations, reads changelogs, scopes impact, and documents deferred work clearly.
Use case: A team needs to fix security advisories and modernize React, TypeScript, and test tooling without creating a single high-risk mega-commit.

Quick Start

Use the dependency-upgrade skill to review my repository’s outdated packages, propose a safe upgrade order, and execute each batch with verification and commit-ready summaries.

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

To safely upgrade dependencies, you should separate low-risk patches from high-risk major updates. This skill plans dependency upgrades in risk-based batches, requiring verification and testing between each group to catch regressions early.

What is the best way to handle major version package upgrades in Node or Python projects?▼

The best way to handle major package upgrades is to isolate them from minor updates. This skill scopes the impact of major version migrations, reads changelogs, and documents deferred work to ensure breaking changes are managed safely.

Can I batch dependency upgrades by risk level for different programming languages?▼

Yes, you can batch dependency upgrades by risk level for Node, Python, Rust, Ruby, and Go projects. The process separates dev dependencies, runtime patches, and major updates so the safest package upgrades land first.

How do I fix security vulnerabilities in dependencies without creating a high-risk mega-commit?▼

Fixing security vulnerabilities safely requires applying patched updates in isolated batches. This skill executes dependency upgrades incrementally, verifying builds and tests after each batch to avoid bundling multiple breaking changes into a single commit.

What should I do if a major dependency upgrade breaks my build verification process?▼

If a major dependency upgrade breaks build verification, you should isolate the change and review the package changelog. This skill isolates major-version migrations and documents deferred work to handle breakage without halting low-risk upgrades.