Dependency Upgrade
Upgrade one dependency at a time by reading its changelog, planning for breaking changes, updating code and proving it still builds and passes. Use to bump, update or migrate a package.
Install
/plugin marketplace add agentkitco/agentkit-dev-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add agentkitco/agentkit-dev-skills --skill dependency-upgradegit clone --depth 1 https://github.com/agentkitco/agentkit-dev-skills.git /tmp/agentkit-dev-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agentkit-dev-skills/skills/dependency-upgrade ~/.claude/skills/dependency-upgradePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Upgrade a dependency safely Goal: move one dependency (or one tightly coupled group) to a newer version with the breakage understood in advance, not discovered afterwards. ## Plan 1. **Pin down the current state.** Find the installed version (lockfile, not just the manifest) and the target version. If the user said "latest", look it up with the package manager (`npm view <pkg> version`, `pip index versions <pkg>`, `cargo search`, etc.) and state the number. 2. **Record a baseline** on a clean working tree: install, build, tests, lint, type check. Note any pre-existing failures so you do not blame the upgrade for them. 3. **Read the real release notes.** Open the changelog, release notes or migration guide for every version between current and target. Extract: breaking changes, removed or renamed APIs, new minimum runtime versions, changed defaults, deprecations. Quote the source link for each item. If you cannot find release notes, say so and treat the upgrade as higher risk. 4. **Map the impact.** `rg` the codebase for each removed, renamed or changed API. List affected files before editing.
Details
- Skill name
dependency-upgrade- Repository
- agentkitco/agentkit-dev-skills
- Path
skills/dependency-upgrade/SKILL.md- License
- MIT
- Repo updated
- 12 November 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Dependency Upgrade skill do?
Upgrade one dependency at a time by reading its changelog, planning for breaking changes, updating code and proving it still builds and passes. Use to bump, update or migrate a package.
How do I install the Dependency Upgrade skill?
Claude Code plugin: /plugin marketplace add agentkitco/agentkit-dev-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Related skills
Agents Md Audit
agentkitco/agentkit-dev-skills
Audit an AGENTS.md, CLAUDE.md, Cursor rule or Copilot instructions file for stale commands, broken paths, vague rules, secrets and contradictions. Use to review or trim agent instructions.
Brag Doc From Git
agentkitco/agentkit-dev-skills
Build an evidence-based brag doc or self-review draft from your merged PRs and commits, leaving visible gaps where results are unknown. Use for review season, promotion cases or resumes.
Explain Codebase
agentkitco/agentkit-dev-skills
Map an unfamiliar repo covering purpose, entry points, how to run it, main modules, data flow and risky areas, with file references. Use when asked to explain or onboard onto a codebase.
PR Description
agentkitco/agentkit-dev-skills
Write a pull request title and description from the actual diff and commits, with what changed, why, how it was tested and what to review. Use when asked to write or improve a PR description.
Review My Diff
agentkitco/agentkit-dev-skills
Self-review uncommitted or branch changes before a PR, with findings ranked by severity and backed by file and line evidence. Use when asked to review my changes or check my diff.
Report
danybgoode/golden-frijoles
Posts a project report to a chat destination, at the cadence asked for. Daily: a delta-only standup of overnight signals across every repo the project spans (opened/merged PRs and CI, the latest browser smoke, BUILD-ORDER drift, open-PR state, stale previews). Weekly: an executive recap/retro (merged PRs, shipped epics, deploys per app repo, a retro digest). PMO: the weekly operational report with scrum/DORA/doc-ops metrics and a story deck, or the on-demand monthly stakeholder packet with a metrics sheet. Use when the product owner asks to "post the standup", "run the daily standup", "what ha
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.