| name | dependency-upgrade |
| description | Safe dependency upgrades — review changelogs, check breaking changes, update lockfile, verify compatibility. Trigger on /dependency-upgrade, or when upgrading packages, fixing vulnerabilities, or migrating library versions. |
| user-invocable | true |
| allowed-tools | Read, Grep, Glob, Bash, Edit |
Dependency Upgrade
Upgrade dependencies safely — prevent agent from updating blindly and breaking the project.
Workflow
1. Identify scope
- Which package(s) to upgrade? Specific version or latest?
- Is it a patch/minor/major update?
- Any related packages that must be upgraded together?
2. Research before upgrading
- Read the changelog / release notes for the new version.
- Check for breaking changes, deprecations, and migration guides.
- Search GitHub issues for known problems with the new version.
- Verify compatibility with the project's Node/Bun/runtime version.
3. Upgrade and verify
- Use the project's package manager (
bun update, pnpm update, npm update).
- Never force-upgrade without understanding the changes.
- Run the project's build / compile step.
- Run tests related to the upgraded package.
- Check lockfile diff for unexpected changes.
4. Breaking changes protocol
- If breaking changes exist, plan migration steps.
- Do not upgrade if migration is incomplete and the old version is still supported.
- If the package has a migration guide, follow it step by step.
- Test the migration in isolation before committing.
5. Report
- What was upgraded (from → to).
- Breaking changes encountered and how they were handled.
- Test results before and after.
- Any pinned versions and why.
Rules
- Always read changelog before upgrading.
- Do not upgrade multiple unrelated packages in one step.
- If CI/tests fail after upgrade, rollback or fix before moving on.
- Security fixes get priority — but still verify they don't break things.
Experience Log
This skill learns from experience. Mechanism:
- Read
.claude/experience/'"$s"'.md at skill start to benefit from past lessons.
- Write to
.claude/experience/'"$s"'.md after use if you learned something new.
- Format:
YYYY-MM-DD: <lesson> — one line per entry.
- Evolve: If the same issue repeats 3+ times, update this SKILL.md itself.
