dependency-upgrade
Skill0 starsChanged 6 days agoMITView on GitHub
Upgrade a dependency, framework or runtime to a new version, especially a major one (React, Next.js, Django, Rails, Node, Python, a library with breaking changes). Use when the user says "upgrade X", "bump to v5", "fix this deprecation", or a security advisory requires a newer version.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- juzorei/bumpmaptheir own version, first seen Nov 15, 2026
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- HyperVon/agent-guidance-kittheir own version, first seen Nov 1, 2026
- navikt/copilottheir own version, first seen Nov 1, 2026
- agentkitco/agentkit-dev-skillstheir own version, first seen Nov 1, 2026
- Eliahhango/nullbyte-securitytheir own version, first seen Nov 1, 2026
Used with
Projects with it also use incident-response, tdd and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillincident-response
Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 4 projects that use this
- GoogleSkill
grill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- secondsky/sap-skills★ 462same name
- navikt/copilot★ 61same name
- xfstudio/skills★ 9same name
- KhaledSaeed18/dotclaude★ 5same name
- Eliahhango/nullbyte-security★ 4same name
- juanitourquiza/shipframe★ 4same name
- WST2002/claude-code-skills★ 4same name
- 0disoft/mcp-security-proxy★ 2same name
- ai4brands-design/claude-skills★ 2same name
- CodeWithBehnam/cc-docs★ 2same name
15 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- api-docsSkill
- changelogSkill
- ci-failure-fixSkill
- code-reviewSkill
- commit-messageSkill
- competitor-analysisSkill
- data-analystSkill
- debug-detectiveSkill
- dockerizeSkill
- email-replierSkill
- eval-promptSkill
- incident-postmortemSkill
- meeting-notesSkill
- migration-safetySkill
- pr-descriptionSkill
- product-specSkill
- readme-writerSkill
- refactor-safelySkill
- research-briefSkill
- security-checkSkill
- seo-articleSkill
- sql-helperSkill
- support-replySkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 20
If you cannot open the changelog, say so and work from compiler errors and tests, flagging that behaviour changes may be missed.
- Distinctive: line 24
Run the test suite, type check, lint and build on the current version first.
- Distinctive: line 29
Update with the package manager so the lockfile changes properly.
- Distinctive: line 30
After each step: install, build, type check, tests.
- Distinctive: line 31
Search the code for every removed or renamed API listed in the guide (git grep), not only the ones the compiler finds.
- Distinctive: line 35
Read the error against the migration guide first.
- Very specific: line 36
Do not silence it with any, @ts-ignore, --legacy-peer-deps, --force or version overrides unless there is no other way.
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Upgrade a dependency
1. Know where you are and where you go
- Current version from the lockfile (the installed one, not only the range in the manifest) and the target version. If the user said "latest", look it up and state the exact number.
- The package manager and its version (npm, pnpm, yarn, pip, poetry, uv, bundler, cargo, go).
- Why: security fix, needed feature, end of support. It decides how far to go.
2. Read before touching
- The changelog and the official migration guide for every major version between current and target. Do not skip intermediate majors: their breaking changes still apply.
- Peer dependencies and plugins that must move together (types packages, framework plugins, lint configs).
- The minimum runtime version the new release needs.
- Codemods the maintainers publish. Prefer them to manual edits.
- If you cannot open the changelog, say so and work from compiler errors and tests, flagging that behaviour changes may be missed.
3. Get a baseline
Run the test suite, type check, lint and build on the current version first. Record what already fails so you do not blame the upgrade for it.
4. Upgrade in steps
- One major version at a time for big jumps. One package (or one group that must move together) per commit.
- Update with the package manager so the lockfile changes properly. Do not hand-edit lockfiles.
- After each step: install, build, type check, tests. Fix what breaks before going further.
- Search the code for every removed or renamed API listed in the guide (
git grep), not only the ones the compiler finds. Behaviour changes (defaults, ordering, timezones, error types) do not show up as compile errors.
5. When something breaks
- Read the error against the migration guide first.
- Do not silence it with
any,@ts-ignore,--legacy-peer-deps,--forceor version overrides unless there is no other way. If you must, list each one in the report. - Stuck after reasonable effort? Stop at the last green step, commit it, and report what blocks the next one.
Report
- From version, to version, and the intermediate steps taken.
- Breaking changes that affected this code and how each was handled.
- Results of build, type check and tests (before and after).
- Workarounds or suppressions added, and follow-ups.
- What to check manually (behaviour changes not covered by tests).
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.