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.
In this repository19 other files it gives its agents.
- agent-handoff-briefSkill
- api-doc-to-tool-specSkill
- architecture-rfc-reviewSkill
- bug-report-to-reproSkill
- changelog-to-upgrade-planSkill
- competitive-research-briefSkill
- customer-call-to-prdSkill
- database-migration-risk-reviewSkill
- incident-log-to-postmortemSkill
- messy-notes-to-decision-logSkill
- privacy-data-flow-mapSkill
- prompt-to-eval-rubricSkill
- repo-launch-readiness-reviewSkill
- roadmap-to-release-planSkill
- security-review-checklistSkill
- support-ticket-to-evalSkill
- telemetry-to-product-insightsSkill
- tool-permission-auditSkill
- workflow-automation-scoutSkill
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
- Distinctive: line 14
Use when a dependency version change needs impact, test, and rollout review.
- Distinctive: line 15
Do not use when choosing between unrelated packages.
- Distinctive: line 29
Call out whether more source inspection is required.
- Distinctive: line 47
Test plan matches likely local impact.
≈ “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.
Files
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.
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
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.

