agentleFS
alexzhu0alexzhu0/agent-ready-skills/skills/dependency-upgrade-risk-review/SKILL.md

dependency-upgrade-risk-review

Skill0 starsChanged 5 months agoMITView on GitHub

Use when reviewing dependency upgrades, package-lock diffs, SDK version changes, release notes, or migration guides for breaking changes, security impact, tests, and rollout risk.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Use when a dependency version change needs impact, test, and rollout review.

    line 14
  2. Distinctive:

    Do not use when choosing between unrelated packages.

    line 15
  3. Distinctive:

    Call out whether more source inspection is required.

    line 29
  4. Distinctive:

    Test plan matches likely local impact.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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 Risk Review

Purpose

Assess whether a dependency upgrade is safe, risky, or needs a staged rollout.

Fit

  • Use when a dependency version change needs impact, test, and rollout review.
  • Do not use when choosing between unrelated packages; use a dependency-selection workflow instead.

Inputs

  • Current and target versions.
  • Changelog, release notes, migration guide, lockfile diff, or package manifest.
  • Local usage patterns and test coverage if available.

Workflow

  1. Identify version jump size and release date distance.
  2. Extract breaking changes, security fixes, deprecations, and runtime changes.
  3. Map changes to likely local usage.
  4. Recommend tests, canary scope, and rollback.
  5. Call out whether more source inspection is required.

Output

Produce Markdown with:

  • Upgrade Snapshot
  • Breaking Changes
  • Local Impact
  • Security And Maintenance Notes
  • Test Plan
  • Rollout Recommendation
  • Open Questions

Validation

  • Version numbers are exact.
  • Changelog claims are not mixed with guesses.
  • Test plan matches likely local impact.
  • Security fixes are visible.
  • Recommendation includes confidence and remaining unknowns.

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.