Skip to content
Back to skills

Dependency Upgrade

ASecurity

Upgrade a dependency or framework through verified compatibility, migration guidance, reproducible installs, and relevant runtime checks.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 13, 2026
ai-agentsgit

Security analysis

A100/100

Scanned October 13, 2026

npx -y skills add sujith011/agentic-pro-skills --skill dependency-upgrade --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dependency Upgrade?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dependency Upgrade
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sujith011-dependency-upgrade/badge)](https://www.skillsdirectory.com/skills/sujith011-dependency-upgrade)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dependency-upgrade
description: "Upgrade a dependency or framework through verified compatibility, migration guidance, reproducible installs, and relevant runtime checks."
---

# Dependency Upgrade

## Process
1. Record installed and target versions, runtime/toolchain requirements, direct/transitive dependents, and why the upgrade is needed.
2. Read the target's official release/migration notes and package metadata. Verify current support and known issues rather than assuming a newer version is compatible.
3. Choose the smallest coherent upgrade set. Framework peers or tightly coupled packages may need to move together; unrelated packages do not.
4. Preserve the existing lockfile workflow. Review codemods before running them, keep user edits intact, and inspect generated/configuration changes.
5. Check clean dependency resolution, type/build checks, changed behavior, and the relevant runtime/integration path. Audit output alone does not prove compatibility.
6. Document unavoidable contract/data changes and rollback feasibility. Compare package and lockfile changes for unexpected sources, scripts, or unrelated updates.

## Example
An ORM major upgrade changes transaction behavior. Update its required peer/runtime versions together and exercise a failed transaction followed by a valid request; a successful compile is insufficient.

## Stop conditions
Do not use force, ignore-peer flags, or a blanket latest upgrade to suppress unexplained conflicts. Release rollback may require data compatibility as well as the previous lockfile.

## Evidence
- Current/target versions and primary migration sources.
- Lockfile diff and clean install result.
- Relevant runtime checks and unresolved compatibility limits.

## Reference
Workflow independently written after reviewing [dependency-upgrade](https://github.com/sickn33/agentic-awesome-skills/blob/cb30121a2dfd007531bd2fbefb56f68de927da6a/skills/dependency-upgrade/SKILL.md).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.