agentleFS
juanitourquizajuanitourquiza/shipframe/skills/dependency-upgrade/SKILL.md

dependency-upgrade

Skill4 starsChanged 21 days agoMITView on GitHub

Safely plan and verify dependency upgrades with compatibility, security, and rollback evidence.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use grill-me.

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.
  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    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, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check primary release notes and migration guidance for the target range.

    line 11
  2. Distinctive:

    Use the package manager and shell available on Claude Code, Codex CLI, or OpenCode.

    line 18

“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

Intent: deps_upgrade — EN: dependency upgrade, update packages, bump library. ES: actualizar dependencias, subir versión de paquetes, actualización de librerías.

  1. Identify the package manager, lockfiles, target dependency, current/resolved version, supported runtime, and reason for upgrading.
  2. Check primary release notes and migration guidance for the target range. Preserve lockfile/package-manager consistency; do not mass-upgrade unrelated packages.
  3. Review direct and transitive impact, breaking changes, security advisories, license changes, and peer/runtime constraints.
  4. Upgrade the smallest coherent set. Run install in the repository's immutable/CI mode where available, plus focused tests, full relevant suite, lint/typecheck/build.
  5. Report exact before/after versions, commands and outcomes, unresolved advisories, and rollback path. Do not claim production compatibility without deployment/runtime evidence.

Host limits

Use the package manager and shell available on Claude Code, Codex CLI, or OpenCode. Never run global upgrades, alter user-level configuration, or fetch private registries without explicit authorization.

Resumen (ES)

Identifica gestor, lockfiles y versiones; consulta notas oficiales, evalúa compatibilidad y actualiza el conjunto mínimo. Ejecuta pruebas/build y registra versión anterior/nueva, advisories y rollback; no hagas upgrades globales.

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.