update-deps
Skill4 starsChanged 20 days agoMITView on GitHub
Update project dependencies (npm packages + GitHub Actions) safely, in staged and separately-verified commits. Use when the user wants to upgrade, bump, or update dependencies.
- Deletes or force-pushes
- Installs packages
- Commits and pushes
20 other projects use a version of this.
Adopted by
Most recently taken up by
- gaia-react/gaiatheir own version, first seen Nov 15, 2026
- backnotprop/plannotatortheir own version, first seen Nov 13, 2026
- pydantic/logfiretheir own version, first seen Nov 3, 2026
- idimsh/tdds-business-skillstheir own version, first seen Nov 1, 2026
- gaia-harness/gaiatheir own version, first seen Nov 1, 2026
- venables/skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use plan and tdd.
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.
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
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 3 projects that use this
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- RSSNext/Folo★ 39ksame name
- microsoft/graphrag★ 37ksame name
- assistant-ui/assistant-ui★ 13ksame name
- backnotprop/plannotator★ 12ksame name
- pydantic/logfire★ 4.6ksame name
- authgear/authgear-server★ 2.1ksame name
- mozilla/bedrock★ 1.3ksame name
- VinkyDev/vibestart★ 295same name
- stella/stella★ 274same name
- github/rust-gems★ 139same name
10 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.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
4
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
- Distinctive: line 58
Ask the user how far to go: safe only, safe plus specific majors, or everything.
- Distinctive: line 72
Read the official upgrade guide (fetch it.
- Distinctive: line 75
Verify (section 5), then commit with a message saying what broke and how you migrated it.
- Very specific: line 82
After a satori, @resvg/resvg-js or culori bump, open a few dist/og/.png.
- Distinctive: line 94
Commit the regenerated lock.
“Common” is measured: kept by at least 6 in 10 of the 20 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
Update dependencies
Bump dependencies in stages, one commit per stage, verifying each, so a regression is easy to bisect and revert. Never bump everything in one shot.
0. Baseline
Work on a branch or a dedicated worktree, with a clean tree. Confirm the project is green before changing anything:
npm install
npm run build && npm run check && npm run lint && npm run format:check
npm audit # record the starting count1. Categorize
npm outdated- Safe: the
Wantedcolumn (within the current semver range). - Major:
Latest>Wanted. Breaking; handle one at a time.
2. Security audit
npm auditNever run npm audit fix --force blind. It often "fixes" by downgrading to an ancient major (it proposes @lhci/cli@0.1.0, which breaks the tool). Read each advisory and decide.
Find where the vulnerable package sits with npm ls <pkg>, then:
- Direct dep with a forward fix: bump it like any other update. Prefer this.
- Transitive dep whose parent has a newer release: bump the parent.
Transitive dep with no forward fix (the parent is already latest): pin the patched version in
overridesinpackage.json, reinstall, re-audit:"overrides": { "tmp": "^0.2.7", "uuid": "^11.1.1", "@tailwindcss/typography": { "postcss-selector-parser": "^6.1.5" } }Use a global override when
npm ls <pkg>shows only one parent chain. Scope it under the parent (as with@tailwindcss/typographyabove) when other consumers still need the old version. An override can cross a major, so check the owning tool still runs: a cleannpm auditisn't enough. For@lhci/cli, runnpx lhci healthcheck.
Weigh the blast radius. A vuln in a dev/CI-only tool (Lighthouse, Prettier, ESLint) never reaches visitors; don't force a risky override for it. Commit any overrides change on its own (fix(deps): …).
Deprecation warnings (npm warn deprecated …) are maintainer notices, not advisories. If the parent still requires the old version, leave it until upstream updates. Only chase one when it has a matching npm audit advisory or the parent is your own direct dep.
3. Confirm scope
Ask the user how far to go: safe only, safe plus specific majors, or everything. Majors can be large migrations.
4. Stage the work, one commit per bump
Safe updates, all at once:
npm update
npm run build && npm run check && npm run lint
git commit -am "chore(deps): apply safe within-range dependency updates"Each major, separately:
- Read the official upgrade guide (fetch it; don't trust memory for recent versions).
npm install <pkg>@^<major>. Install coupled packages together (see the notes at the end).- Apply the code/config migration.
- Verify (section 5), then commit with a message saying what broke and how you migrated it.
5. Verify every stage
npm run build,npm run check,npm run lint.npm run format, so CI'sformat:checkpasses. A Tailwind bump can produce wide class-reorder diffs; they're cosmetic.- Runtime, not just a green build: start
npm run previewandnpm run dev(the Vite dev path differs),curlreal pages at the URL each prints, then stop them withnpx astro preview stop/npx astro dev stop. Confirm the stylesheet loads and the content pipeline output is intact: copy buttons (data-copy-button), external links (data-external), Shiki (astro-code). See/run. - After a satori, @resvg/resvg-js or culori bump, open a few
dist/og/**.png. A broken font/color pipeline still builds but produces blank or black cards.
6. Lockfile hygiene
Incremental installs can leave package-lock.json missing cross-platform optional deps (e.g. Tailwind 4's @tailwindcss/oxide bindings and @emnapi/*). CI's npm ci then fails with EUSAGE … Missing: <pkg> from lock file. After the majors, regenerate and validate the way CI does:
rm -rf node_modules package-lock.json
npm install
npm ci # must succeed; this is what CI runsCommit the regenerated lock.
7. GitHub Actions
Actions are pinned by major tag. List them with their latest release:
grep -rn "uses:" .github/workflows/
for a in $(grep -rhoE "uses: [^@]+" .github/workflows/ | awk '{print $2}' | sort -u); do
echo "$a -> $(gh api repos/$a/releases/latest --jq .tag_name)"
doneBump each uses: <action>@vN to the latest major. For github-script, skim the inline script:; v8/v9 keep github.rest.*, context.* and require.
Node and npm versions
.node-version(exact, e.g.24.22.1) is the one pin. CI reads it (actions/setup-nodewithnode-version-file: .node-version), and so do Cloudflare Pages and Netlify. Cloudflare reads nothing else, so a missing or stale file falls back to an older Node. The build scripts (node scripts/*.tsinprebuild) need Node ≥ 24's native type-stripping; on older Node the deploy fails withERR_UNKNOWN_FILE_EXTENSIONeven when CI is green.package.jsonengines.node(">=24") is the floor, not a pin. Vercel reads its major. Raise it only for a new Node major, and keep@types/nodeon the pinned major.- AWS Amplify reads neither; set the Node version in its build settings (or
nvm useinamplify.yml) to match.node-version. - npm isn't pinned separately: each Node release bundles its npm. (Don't add
packageManager; it relies on corepack, which newer Node no longer bundles.)
On each pass, bump .node-version to the latest patch of its major (patches are often security releases):
curl -s https://nodejs.org/dist/index.json | python3 -c "import json,sys; m=open('.node-version').read().split('.')[0]; print(next(r['version'] for r in json.load(sys.stdin) if r['version'].startswith('v'+m+'.')))"
grep -H . .node-version; grep -n '"node"' package.json; grep -rn node-version .github/workflows/Move to a new Node major only once it's LTS, as its own commit.
8. PR and CI
git push -u origin <branch>
gh pr create --base main --title "chore(deps): …" --body "…"
gh pr checks <PR#> --watch --interval 15Both ci and lighthouse must pass. If ci fails within seconds at "Install dependencies", it's the lockfile: go back to section 6.
In a worktree, gh pr merge --delete-branch fails with 'main' is already used by worktree. The merge still lands; delete the branch with git push origin --delete <branch>.
Project-specific migration notes
- Astro 7 Markdown defaults to the Sätteri processor, which doesn't run remark/rehype plugins. This project needs its custom rehype plugins,
remarkRehypehandlers and Shiki, so it uses the unified pipeline:@astrojs/markdown-remarkandmarkdown.processor: unified(markdownPipeline)inastro.config.mjs, with the plugins (fromsrc/markdown/) passed insideunified({...})(Astro 7.4 deprecates the oldmarkdown.remarkPlugins/rehypePlugins/remarkRehypekeys). MDX 8 needs@astrojs/markdown-remark7.3 or later. - Content Layer: collections live in
src/content.config.tswithglob()loaders (astro/loaders). Entries use.id(not.slug) andrender(entry)fromastro:content(notentry.render()).entry.bodyisstring | undefined; guard it. - Tailwind 4 uses the
@tailwindcss/viteplugin inastro.config.mjs; the old@astrojs/tailwindintegration caps Astro at 5, so Astro 7 and Tailwind 4 move together. Styles enter viasrc/styles/global.css(@import "tailwindcss"), imported inBaseLayoutandBrandLayout.tailwind.config.mjsis loaded with@config. There's no JSsafelist; use@source inline("…")for classes the scanner can't see (the rehype-injected copy-button classes). Check/-/astro/brand/color/still renders. @lhci/cliaudit noise (dev-only): the remainingnpm auditfindings and most deprecation warnings trace to@lhci/cliand its Lighthouse sub-deps. It's already latest, so there's no forward fix, andaudit fix --forcewould downgrade it to 0.1.0. Thetmpanduuidoverrides clear the advisories they target; confirm withnpx lhci healthcheck. Theinflight/rimraf@3/glob@7warnings come fromchrome-launcherand carry no advisory. Leave them: forcingrimraf@4+(callback API removed) breaks chrome-launcher's temp-profile cleanup.
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.

