Dependency upgrade risk review
Skill alexzhu0/agent-ready-skills/skills/dependency-upgrade-risk-review
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.From its SKILL.md
npx -y skills add alexzhu0/agent-ready-skills --skill dependency-upgrade-risk-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 244 tokens by cl100k_base, as published. Nobody here has run it
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
- Identify version jump size and release date distance.
- Extract breaking changes, security fixes, deprecations, and runtime changes.
- Map changes to likely local usage.
- Recommend tests, canary scope, and rollback.
- 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.