agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/dependency-upgrade/SKILL.md

dependency-upgrade

Skill1 starsChanged 41 days agoMITView on GitHub

Upgrade dependencies safely with minimal risk. Use when bumping packages, resolving CVEs, or updating major versions.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use incident-response, grill-me and 1 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

    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

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

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 3

    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. Distinctive:

    Prefer the project’s package manager and lockfile workflow.

    line 11
  2. Very specific:

    Run install, then tests/typecheck/build.

    line 13
  3. Distinctive:

    Do not upgrade unrelated packages opportunistically.

    line 19
  4. Distinctive:

    Commit lockfile and manifest together.

    line 23

“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

Process

  1. Identify current version, target version, and changelog/breaking notes.
  2. Prefer the project’s package manager and lockfile workflow.
  3. Upgrade the smallest set that achieves the goal (one package or related group).
  4. Run install, then tests/typecheck/build.
  5. Fix breakages caused by the upgrade only.
  6. Summarize behavioral or API changes that affect the app.

Rules

  • Do not upgrade unrelated packages opportunistically.
  • Pin/lock according to repo convention.
  • For majors: read migration guides before editing call sites.
  • For security advisories: confirm the advisory applies to the used code path.
  • Commit lockfile and manifest together.

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