dependency-upgrade

Plans, executes, and audits dependency upgrades across npm, Composer, pip, Go, and Cargo.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill dependency-upgrade-jose-polanco-oxte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-upgrade
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/dependency-upgrade
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill dependency-upgrade-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Upgrading dependencies blindly causes broken builds, hidden breaking changes, and exposure to compromised package versions. This Skill turns version bumps into a sequenced, evidence-backed process with changelog review, call-site analysis, verification gates, and supply-chain audits. ## Core Features & Use Cases - Changelog-Driven Planning: Pin exact versions from the lockfile, read migration guides for every intermediate major, and map breaking changes to actual call sites in your codebase via grep. - Per-Stack Execution Workflows: Step-by-step upgrade commands and verification pipelines for Composer/PHP, npm/pnpm/yarn, pip/poetry/uv, Go modules, and Cargo, with one-major-at-a-time sequencing and rollback plans. - Supply-Chain Security Audit: Detect compromised updates that CVE scanners miss by diffing install scripts, transitive dependencies, network capabilities, and provenance between old and new versions. - Use Case: A Dependabot alert forces a React upgrade from v17 to v19. Use this Skill to map the version path, identify which breaking changes touch your code, upgrade one major at a time behind green tests, and audit the new versions for malicious behavior before merging. ## Quick Start Plan and execute a safe upgrade of my project's lodash dependency to the latest version, including a security audit of the new release.

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 a dependency across multiple major versions?

Upgrade one major version at a time, landing each step behind a green build and test run. Read the migration guide for every intermediate major, map breaking changes to your actual call sites with grep, and record a rollback plan before starting.

How to detect a compromised or malicious package update?

Install with scripts disabled, then diff the old and new versions for new install hooks, new transitive dependencies, unexpected network or filesystem capabilities, and lost provenance. CVE scanners miss fresh compromises, so a behavior audit is required.

Does this upgrade workflow support Python and Go projects?

Yes, the execution reference covers pip, poetry, and uv for Python plus go.mod for Go, alongside Composer, npm, and Cargo. Each stack has specific outdated-check, upgrade, audit, and verification commands.

Why does npm install succeed but the build break after an upgrade?

Peer-dependency conflicts and bumped minimum runtime requirements often install with only a warning but fail in CI or at runtime. Verify the target's peerDependencies and engines against your repo and CI environment before writing code.

When should I not use npm audit fix --force?

Never apply forced audit remediation automatically, since it can cross declared dependency ranges and introduce breaking changes. Preview the remediation, read the changelogs, and test each resulting upgrade individually.