upgrade-deps
Skill1 starsChanged 16 days agoMITView on GitHub
Update dependencies with this repo's package manager, run the test suite, and fix breakages in this repo's code. Use when the user asks to upgrade dependencies, bump packages, apply dependabot-style updates, or refresh the lockfile. Do not hide breaking changes.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- Kangentic/kangentictheir own version, first seen Nov 8, 2026
- F1bonacc1/process-composetheir own version, first seen Nov 1, 2026
- sebyx07/ruby2htmltheir own version, first seen Nov 1, 2026
- argos-ci/argostheir own version, first seen Oct 17, 2026
- ypxing/coding-crewtheir own version, first seen Oct 13, 2026
- areal-project/AReaLtheir own version, first seen Oct 8, 2026
Used with
Projects with it also use create-pr.
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.
SentrySkillcreate-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- areal-project/AReaL★ 5.9ksame name
- inclusionAI/AReaL★ 5.9ksame name
- line/armeria★ 5.2ksame name
- sorayuki/obs-multi-rtmp★ 5.1ksame name
- F1bonacc1/process-compose★ 2.9ksame name
- argos-ci/argos★ 657same name
- Kangentic/kangentic★ 140same name
- sebyx07/ruby2html★ 23same name
- dennisrongo/claude-skills★ 1same name
- ypxing/coding-crew★ 1same name
1 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 repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- commitSkill
- cut-releaseSkill
- data-changeSkill
- debugSkill
- engineering-barSkill
- explain-codeSkill
- explore-codebaseSkill
- fix-ciSkill
- handoffSkill
- implement-changeSkill
- incident-triageSkill
- lean-reviewSkill
- open-prSkill
- performanceSkill
- production-passSkill
- ready-to-mergeSkill
- record-decisionSkill
- refactor-safelySkill
- resolve-conflictsSkill
- revert-changeSkill
- review-changeSkill
- security-passSkill
- shape-workSkill
- ship-notesSkill
- start-projectSkill
- verify-uiSkill
- write-architectureSkill
- write-designSkill
- write-dev-tasksSkill
- write-docsSkill
- write-prdSkill
- write-testsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 9 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
6
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 14
Read AGENTS.md if present.
- Distinctive: line 18
Use the lockfile / manifest that exists.
- Distinctive: line 40
If several ecosystems exist (monorepo), stay in the package the user named, or one ecosystem per run.
- Distinctive: line 44
Default: the packages the user named.
- Very specific: line 46
Prefer this repo's existing upgrade path (Renovate/Dependabot config, a make deps target, npm outdated)
- Distinctive: line 49
Write the planned list before editing: name, from → to, major bump yes/no.
- Distinctive: line 51
Do not upgrade a package that is vendored or pinned in AGENTS.md Do not edit without asking.
- Distinctive: line 56
Run the manager's update command for the planned set.
- Distinctive: line 57
Do not hand-edit a lockfile if the manager can write it.
- Very specific: line 58
Do not add new packages here (implement-change does that).
- Very specific: line 62
Run Test, then Lint / Typecheck / Build if known.
- Very specific: line 67
Follow debug if the cause is unclear
- Distinctive: line 68
Do not delete tests, skip cases, or pin the old version in a new override without telling the user
- Very specific: line 69
If the upgrade is a major and the fix is large, stop, revert the dep bump, and report the breakage.
- Very specific: line 85
Do not commit unless asked.
“Common” is measured: kept by at least 6 in 10 of the 11 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 deps
Move dependencies forward without lying about compatibility. Do not swallow a breaking change by weakening tests or pinning * ranges this repo does not already use.
Read AGENTS.md if present.
Detect the manager
Use the lockfile / manifest that exists. Do not add a second manager.
| Evidence | Manager |
pnpm-lock.yaml | pnpm |
yarn.lock | yarn |
bun.lock / bun.lockb | bun |
package-lock.json | npm |
uv.lock / poetry.lock / Pipfile.lock | uv / poetry / pipenv |
requirements.txt + no other lock | pip (say it is weaker) |
Cargo.lock | cargo |
go.sum | go |
Gemfile.lock | bundler |
composer.lock | composer |
pom.xml / maven-wrapper.properties | maven |
build.gradle / build.gradle.kts / gradle.lockfile | gradle |
*.csproj / packages.lock.json / Directory.Packages.props | dotnet / nuget |
Package.resolved | swiftpm |
pubspec.lock | dart / flutter (pub) |
flake.lock | nix |
.terraform.lock.hcl | terraform |
If several ecosystems exist (monorepo), stay in the package the user named, or one ecosystem per run.
Scope
Default: the packages the user named. If they said "all" or "latest":
- Prefer this repo's existing upgrade path (Renovate/Dependabot config, a
make depstarget,npm outdated) - Otherwise update within the same major unless the user asked for majors
Write the planned list before editing: name, from → to, major bump yes/no.
Do not upgrade a package that is vendored or pinned in AGENTS.md Do not edit without asking.
Apply
- Record the current lockfile hash / git status (clean tree preferred; if dirty, only touch dep files or stop).
- Run the manager's update command for the planned set. Match commands this repo already uses in CI or README.
- Do not hand-edit a lockfile if the manager can write it.
- Do not add new packages here (
implement-changedoes that). This skill only changes versions of existing deps.
Prove
Run Test, then Lint / Typecheck / Build if known. If a command is (unknown), say unverified for that check.
On failure:
- Fix this repo's call sites (types, renamed APIs, import paths)
- Follow
debugif the cause is unclear - Do not delete tests, skip cases, or pin the old version in a new override without telling the user
- If the upgrade is a major and the fix is large, stop, revert the dep bump, and report the breakage. Offer
shape-workfor an adoption change
Load engineering-bar (paths in that skill) on any product-code edits.
Done
## Upgrade
- Manager:
- Changes: <name from → to>
- Majors:
- Commands: <test/lint + exit status>
- Product-code fixes:
- Left on old version (and why):Do not commit unless asked. Next: ready-to-merge if product code changed, then commit. Mention ship-notes if this repo logs dependency bumps in the changelog.
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.