dependency-upgrades
Skill0 starsChanged 6 days agoMITView on GitHub
Verify npm/pnpm upgrades and JavaScript toolchain replacements beyond install success: peer-policy masking, hook rewrites, linter parity and artifact compatibility. Use when upgrading dependencies, fixing advisories or replacing lint, format, compiler or build tools.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- reddygopalkrishna/developer-agent-skillstheir own version, first seen Nov 8, 2026
- d-o-hub/github-template-ai-agentstheir own version, first seen Nov 3, 2026
- issue-orchestrator/issue-orchestratortheir own version, first seen Sep 6, 2026
- Bridev04/clauderailtheir own version, first seen May 17, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- issue-orchestrator/issue-orchestrator★ 10same name
- reddygopalkrishna/developer-agent-skills★ 8same name
- d-o-hub/github-template-ai-agents★ 2same name
- Bridev04/clauderail★ 0same name
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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-work-verificationSkill
- create-taskSkill
- database-migration-reviewSkill
- debug-logsSkill
- fix-prSkill
- pr-merge-gatesSkill
- production-debuggingSkill
- release-verificationSkill
- reliability-reviewSkill
- shipSkill
- workSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
7
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 19
Prefer a narrow transitive/lockfile change where the parent already admits the patch.
- Distinctive: line 21
Check the advertised Node range against every resolved dependency's engines.
- Distinctive: line 27
Keep GitHub alerts, package-manager advisories and unique packages separate.
- Distinctive: line 31
When no patched version exists, inspect the parent upgrade or removal path rather than forcing incompatibility.
- Distinctive: line 43
Import sorting changes module side-effect order.
- Distinctive: line 45
Keep framework route/code generation before typecheck.
- Distinctive: line 51
After runner/filter changes, compare executed file sets and full test-name multisets, not just counts.
- Very specific: line 63
Before handing off manual testing, install the frozen graph and regenerate local clients/types/icons/bundles without schema pushes.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Dependency and toolchain upgrades
Resolution is not compatibility
npm ciwithlegacy-peer-deps=truedoes not establish peer compatibility. Inspect effective npm config and.npmrcfiles. If claiming strict compatibility, run an isolated frozen install with--legacy-peer-deps=false --strict-peer-deps=true; do not silently change the repository's persistent policy.- Lifecycle scripts can rewrite shared Git hooks in worktrees. Record hook state before an install and compare afterwards. Use an authorized script-free install plus explicit generation when appropriate; do not mistake missing generated artifacts for an application defect or weaken hooks to get a green result.
- Query registry metadata for the exact release.
latestcan be a prerelease; aliases and calendar versions need semantic review. Respect release-age policy and report held versions. Compare lockfile integrity for advisories. - Prefer a narrow transitive/lockfile change where the parent already admits the patch. A major override needs testing at the actual consuming boundary, not just an import. Never dismiss an advisory to clear a count.
- Check the advertised Node range against every resolved dependency's engines. A lower bound also promises future majors that dependencies may exclude; update runtime selectors, package metadata and docs together.
- Resolve duplicate framework/SDK copies: registration through one copy may not reach dispatch through another.
Audit evidence
- Keep GitHub alerts, package-manager advisories and unique packages separate. Zero open alerts does not prove the frozen lockfile is clean; equal totals do not prove the same findings. A local fix does not close a default-branch alert. Record audit exit separately from any successful collection wrapper.
- "Unreachable" requires tracing the real consumer, including export/SSR paths that accept stored content. When no patched version exists, inspect the parent upgrade or removal path rather than forcing incompatibility.
Toolchain parity
- Review migrator edits to manifests, catalogs, overrides, scripts, hooks and source. Cached task runners can strip environment overrides; test the real child with a harmless sentinel rather than trusting the wrapper.
- Print resolved linter configuration for source and test files. Trigger each previously enforced rule as a positive control, especially hooks/accessibility and type-aware rules that can silently be disabled.
- Translated suppressions need the new diagnostic span, not just a renamed rule ID. Prove both the intended exception and a fresh violation. A warning-level autofix may still rewrite source in a supposedly check-only lane.
- To claim no formatter churn, format the baseline in a disposable copy and count changed paths. A green check of already-reformatted candidate files proves only a fixed point.
- Import sorting changes module side-effect order; moving a JSX prop across a spread changes precedence. Review execution/AST order, not only token equality. Exercise the real fix/staged-file hook path.
- Keep framework route/code generation before typecheck. API/declaration consumers still using the old compiler make a compiler migration incomplete even if the main typecheck is green.
Tests and deliverables
- A suite named unit can launch a browser. Read fixtures before executing it and retain browser permission gates. After runner/filter changes, compare executed file sets and full test-name multisets, not just counts.
- For wire changes, test the unchanged deployed client's parser. Upgrading both test SDK and server can make them agree on a format old clients reject.
- For package builders, compare ESM/CJS loading, export targets, declarations, sourcemaps, tarball paths and API reports. Equal counts are not parity. Recompute after the final bundler edit; overload and union changes need semantic review even when nearby quote/order changes are cosmetic.
- Cached Turbo/Nx logs are replayed evidence, not fresh execution. Pass force flags to the task runner itself,
not through
--to its child. Container install/prune changes need the real production image target; a host build cannot prove that stage. - Transitive packages can break a pinned parent's imports. Inspect the resolved graph and known-good lockfile before proposing an unrelated major upgrade; test scoped overrides in isolation.
Before handing off manual testing, install the frozen graph and regenerate local clients/types/icons/bundles without schema pushes. State branch, SHA, runtime, executed versus cached gates and unverified image/browser work.
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.

