upgrade-deps
Skill661 starsChanged 7 days agoMITView on GitHub
Upgrade every dependency of the Argos pnpm monorepo to its latest eligible version and close all open Dependabot alerts, ending in one verified pull request whose description lists each security fix. Use whenever someone asks to upgrade, bump or update dependencies or packages, mentions `pnpm upgrade -i -L -r` / `pnpm update -L`, wants Dependabot or npm security alerts fixed, or asks to refresh the lockfile. Use it even for a single vulnerable transitive package, since the release-age, override, patch and held-package checks apply just the same.
- Deletes or force-pushes
- Installs packages
- Commits and pushes
12 other projects use a version of this.
Adopted by
Most recently taken up by
- jameswyse/skillstheir own version, first seen Nov 15, 2026
- Kangentic/kangentictheir own version, first seen Nov 8, 2026
- F1bonacc1/process-composetheir own version, first seen Nov 1, 2026
- rpraharaj/ai-engineertheir own version, first seen Nov 1, 2026
- sebyx07/ruby2htmltheir own version, first seen Nov 1, 2026
- ypxing/coding-crewtheir own version, first seen Oct 13, 2026
Used with
Projects with it also use create-pr, review-pr and 1 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.
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
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- 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
- Kangentic/kangentic★ 142same name
- sebyx07/ruby2html★ 23same name
- dennisrongo/claude-skills★ 1same name
- jameswyse/skills★ 1same name
- rpraharaj/ai-engineer★ 1same name
2 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- argos-cliSkill
- argos-pr-reviewSkill
- argos-uploadSkill
- frontend-designSkill
- lucide-style-iconsSkill
- security-auditSkill
- vercel-react-best-practicesSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 7 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
If the branch name is taken, add the day.
- Very specific: line 43
Read the comments in pnpm-workspace.yaml before upgrading.
- Distinctive: line 62
Run git init in the unpacked package.
- Distinctive: line 63
Run git apply --check with the old patch, apply it (fix context by hand if needed), then git diff --full-index.
- Distinctive: line 73
If it is a CVE floor, raise it to the patched version so the fix cannot regress.
- Very specific: line 75
If it holds a direct dependency below a new major, raise it with that dependency.
- Distinctive: line 78
Do not delete an override you cannot explain.
- Distinctive: line 91
Delete the exclusion and restore the range.
- Very specific: line 93
Put back any catalog: specs that command rewrote to literal versions.
- Very specific: line 96
Duplicates: Run pnpm dedupe. Then look for two copies of a package whose types cross package boundaries, zod above all: grep -oE "^ …
- Very specific: line 106
Peers: Run pnpm peers check again and compare it with the baseline from step 1.
- Very specific: line 127
Read the version's breaking changes at https://docs.stripe.com/changelog/<release name>.
- Distinctive: line 157
Run these in order. Each one is cheaper than the next.
- Very specific: line 184
Before blaming a failure on the upgrade, A/B it.
- Very specific: line 191
Every commit here is chore (see CLAUDE.md: dependency work is never feat or fix).
- Very specific: line 197
Use a separate chore(<scope>) commit for each behavior fix or policy change a reviewer might want to keep apart or drop.
- Very specific: line 219
After gh pr create, watch CI.
“Common” is measured: kept by at least 6 in 10 of the 12 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 dependencies
A human runs pnpm upgrade -i -L -r and picks versions from the interactive
list. An agent cannot drive that picker, so this skill does the same upgrade
non-interactively. It adds the checks that a plain upgrade skips. The result
is one pull request on a fresh branch. It closes every open Dependabot alert
and moves every direct dependency to its latest eligible version. Its
description says what changed, what was held back and why, and what was
tested.
Two bundled scripts do the bookkeeping. Run them from the repository root:
scripts/dependabot_alerts.pychecks each open alert against the lockfile. It exits 1 while any alert still resolves to a vulnerable version. With--markdownit prints the PR's security table.scripts/dep_changes.pylists every range that changed againstorigin/main, grouped as major, minor and patch. It covers manifests, the catalog and overrides.
Both live in .agents/skills/upgrade-deps/scripts/.
1. Start from main
git fetch origin main
git switch -c chore/upgrade-deps-$(date +%Y-%m) origin/main --no-track
pnpm install --frozen-lockfile
python3 .agents/skills/upgrade-deps/scripts/dependabot_alerts.py
pnpm outdated -r
pnpm peers check > <scratch>/peers-before.txtIf the branch name is taken, add the day. The alert list matters: the PR must account for every alert in it. The peer baseline is for step 3.
2. Respect what is held on purpose
Read the comments in pnpm-workspace.yaml before upgrading. A package can be
pinned for a reason that still holds. graphql, for example, stays on 16 until
Apollo Server supports 17. Leave such packages out of the update, and ask
before lifting a hold.
3. Upgrade
pnpm update -L -r '!graphql' # one '!<pkg>' per held packageThen work through what the update cannot do on its own.
A patched dependency moved. A patchedDependencies entry for the old
version stops the update with ERR_PNPM_UNUSED_PATCH, and nothing is
written. First check whether upstream fixed the bug: npm pack the new
version and read the patched file. If the bug is still there, regenerate the
patch:
- Run
git initin the unpacked package. - Run
git apply --checkwith the old patch, apply it (fix context by hand if needed), thengit diff --full-index. - Rename the file and its
patchedDependencieskey to the new version. - Compare the patch's
+/-lines with the old ones usingcmp.
Then run the guard named in the comment above patchedDependencies.
Overrides cap a dependency. pnpm update leaves alone any package an
override controls. Review every entry under overrides:
- If it is a CVE floor, raise it to the patched version so the fix cannot regress.
- If it holds a direct dependency below a new major, raise it with that
dependency. Use
pnpm why <pkg>to see who still depends on it.
Do not delete an override you cannot explain.
The catalog is not updated. Bump catalog: entries in
pnpm-workspace.yaml by hand. Only use versions that pnpm outdated listed.
The 24-hour release age. pnpm 11 refuses versions published less than a
day ago, and pnpm outdated hides them. pnpm config get minimumReleaseAge
prints undefined anyway. A hand-edited range can still pull such a version
in. The next pnpm update then quietly adds it to
minimumReleaseAgeExclude, a permanent exemption. Before committing, read
the diff of that list: only @argos-ci/* belongs there. To undo a too-young
version:
- Delete the exclusion and restore the range.
- Run
pnpm update -r --depth Infinity <pkg>@<previous>. - Put back any
catalog:specs that command rewrote to literal versions. - Run
pnpm install.
Duplicates. Run pnpm dedupe. Then look for two copies of a package
whose types cross package boundaries, zod above all:
grep -oE "^ '?zod@[0-9][^:'(]*" pnpm-lock.yaml | sort -u. Two copies give
type errors that look like code bugs.
Alerts still open. Re-run the alerts script. For a transitive package
that is still vulnerable, run pnpm update -r --depth Infinity <pkg> first.
The fix usually fits the parent's range. Add an override only if that fails,
with a comment saying why.
Peers. Run pnpm peers check again and compare it with the baseline
from step 1. Only issues main did not have matter; an upgrade often clears
some.
4. Review the majors
python3 .agents/skills/upgrade-deps/scripts/dep_changes.py lists them. For
each major, read its release notes or migration guide, then grep the code for
what it touches. Hand the backend and frontend majors to parallel research
subagents, so the reading happens while you verify.
Type checks catch removed APIs. The reading is for what they cannot catch:
changed defaults, timing, wire formats, API versions. Check exact patch
versions too. jotai 3.0.0 broke atomWithStorage restore and 3.0.1 fixed it,
so the range needs a floor of 3.0.1.
Cases that recur. Re-check each one, since upstream moves:
- stripe. Each SDK major pins a new Stripe API version.
apiVersioninapps/backend/src/stripe/index.tsis typed as that exact string, so the type check flags it.- Read the version's breaking changes at
https://docs.stripe.com/changelog/<release name>. Check them against the fieldssrc/stripe/reads and the parameters it sends. - Webhook payloads follow each endpoint's own API version, set in the Stripe Dashboard. List that upgrade as a follow-up for the user.
- Read the version's breaking changes at
- @playwright/test. CI runs e2e in
mcr.microsoft.com/playwright:v<version>-jammy(.github/workflows/ci.yml). Move the tag to the same version, after checking it exists:curl -s https://mcr.microsoft.com/v2/playwright/tags/list. New browsers can shift pixels, so expect the Argos e2e build to show some. - oxfmt. A new version can reformat code. Run
pnpm run formatand commit the result with the upgrade. - turbo. Since 2.11 it appends a managed block to
AGENTS.md(whichCLAUDE.mdlinks to) whenever an agent runs it."agentGuidance": falseinturbo.jsonstops that. CheckAGENTS.mdis unchanged after turbo runs. - @base-ui/react.
- The tooltip patch (see step 3) needs its guard story.
- The menu kit's
closeNowcommits the close withflushSyncbefore unmounting. Base UI 1.9 drops an unmount batched with closing a controlledopen. - On every bump, run
tests/build.spec.ts"says which of the two emptied the snapshot list".
- zod. 4.6.6 reports a
.max()failure insidez.unionas a bare "Invalid input". That breakscreateBuild's 5000-screenshot "parallel mode" error, whichcreateBuild.e2e.test.tsguards. - graphql. Held at 16 (see step 2).
5. Verify
Run these in order. Each one is cheaper than the next.
pnpm buildpnpm run static-checks. This is what CI runs: types, format, lint, knip.pnpm test:unitIntegration tests. They need Postgres, Redis and RabbitMQ:
docker compose up -d. Without RabbitMQ the upload tests time out.PG_DATABASE=deps_upgrade_it npx vitest run --config vitest/vitest.e2e.config.mtsThe private database name keeps other checkouts' runs from dropping yours. Drop the
deps_upgrade_it_*databases afterwards. A timeout under load is not a regression until the file fails on its own too.Storybook. Stop any Storybook dev server of this checkout first: they share a Vite cache. Then, from
apps/frontend:rm -rf node_modules/.cache/storybook npx vitest run --config ./vitest.config.mts --project storybook- Playwright runs in CI. Reproduce a failing spec locally with
references/isolated-e2e.md, which also covers timing failures.
Before blaming a failure on the upgrade, A/B it. Put the suspect package back
to its old version and re-run. If it is a library behavior change, a short
standalone script run against both npm packed versions proves it in
seconds. That is how the zod 4.6.6 change was pinned down.
6. Commit and open the PR
Every commit here is chore (see CLAUDE.md: dependency work is never
feat or fix).
chore(deps): upgrade all dependenciescovers manifests, lockfile, workspace file, patches, the CI image, formatter output and the code changes the majors force.- Use a separate
chore(<scope>)commit for each behavior fix or policy change a reviewer might want to keep apart or drop.
Build the description from the scripts:
python3 .agents/skills/upgrade-deps/scripts/dependabot_alerts.py --markdown
python3 .agents/skills/upgrade-deps/scripts/dep_changes.py --markdownSections:
- Security fixes. The alerts table, every alert linked, with severity, the vulnerable version and the locked one.
- Major upgrades and what they required. One bullet per major, including "no code change" verdicts and why.
- Held back. Each held package and the reason: a policy hold, a release too young, a regression found.
- Follow-ups outside the code. Dashboard settings and similar.
- Test plan. Real counts from step 5. Say which failures were load flakes and how you showed it.
After gh pr create, watch CI. When e2e fails, the Argos build of that run
holds the failure screenshots, because CI uploads no Playwright artifacts.
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.

