agentleFS
Sign inStart free
WST2002WST2002/claude-code-skills/skills/dependency-upgrade/SKILL.md

dependency-upgrade

Skill4 starsChanged 27 days agoMITView on GitHub

Use when upgrading packages, libraries, a framework or a language runtime (React, Next.js, Angular, Spring Boot, Django, Node, Python, Java), fixing outdated or vulnerable dependencies, handling breaking changes after a major version bump, or cleaning up npm audit / Dependabot alerts.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use incident-response, tdd and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    incident-response

    Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

    Also in 3 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 4 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run official codemods: when available (for example npx @next/codemod, npx react-codemod, Angular ng update, OpenRewrite for Spring).

    line 20
  2. Distinctive:

    Upgrade, fix, verify: update the version and lockfile, fix compile and type errors, run lint, tests and build, start the app and check the …

    line 21

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dependency Upgrade

Overview

Upgrade in small, verified steps. Read what changed before changing code, keep the app working after each step, and never mix an upgrade with unrelated changes.

Method

  1. Inventory. List outdated and vulnerable packages: npm outdated / npm audit, pip list --outdated / pip-audit, mvn versions:display-dependency-updates, go list -u -m all. Note current and target versions.
  2. Plan the order:
    • Patch and minor updates first, in one batch.
    • Then each major upgrade on its own, starting with the runtime and framework, then libraries that depend on them.
    • Security fixes before feature upgrades.
  3. Read before changing. For each major upgrade: official migration guide, changelog "Breaking changes" section, deprecation notices from the current version. Check peer dependency requirements.
  4. Run official codemods when available (for example npx @next/codemod, npx react-codemod, Angular ng update, OpenRewrite for Spring).
  5. Upgrade, fix, verify: update the version and lockfile, fix compile and type errors, run lint, tests and build, start the app and check the main flows.
  6. Commit per step with the versions in the message.

Output

Before changing code:

| Package | Current | Target | Type | Breaking changes affecting this project | Effort |

After:

Upgraded: <list>
Code changes: <what was changed and why>
Verified: <lint, tests, build, manual checks>
Not upgraded: <package — reason, e.g. blocked by peer dependency>

Rules

RuleWhy
Lockfile updated and committedReproducible installs
One major upgrade per commit or PREasy review and revert
Search the codebase for every API listed as removed or changedBreaking changes hide in rarely used code
Remove --force / --legacy-peer-deps workarounds once the tree is consistentThey hide real conflicts
Check transitive vulnerabilities with npm audit / pip-audit after upgradingA direct upgrade may not fix them

Common mistakes

  • Upgrading everything at once, then not knowing which package broke the build.
  • Changing versions without reading the migration guide.
  • Silencing deprecation warnings instead of fixing them.
  • Declaring success because it compiles; run the tests and the app.
  • Using npm audit fix --force, which can jump major versions without notice.

Made by Wageesha Tripathi · LinkedIn · Email · More skills

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free