upgrade-dependency
Skill4 starsChanged 5 days agoMITView on GitHub
Upgrade a dependency and adapt every affected call site. Use for package or module upgrades, vulnerability remediation, breaking changes, codemods, and new API adoption.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- fitlab-ai/agent-infratheir own version, first seen Oct 27, 2026
- ModelEngine-Group/fit-frameworktheir own version, first seen Oct 8, 2026
- awcameron/skillstheir own version, first seen Sep 30, 2026
- warsab/ai-skillstheir own version, first seen Aug 26, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- ModelEngine-Group/fit-framework★ 2.1ksame name
- fitlab-ai/agent-infra★ 88same name
- awcameron/skills★ 2same name
- warsab/ai-skills★ 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 repository119 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibilitySkill
- agent-watchdogSkill
- aipSkill
- animateSkill
- animation-performanceSkill
- animation-vocabularySkill
- ask-benSkill
- ask-sonnerSkill
- bazelSkill
- bend-lawsSkill
- blast-radiusSkill
- brain-dumpSkill
- break-uiSkill
- ci-fixesSkill
- codebase-designSkill
- codex-compatSkill
- codexSkill
- commit-push-prSkill
- connect-querySkill
- create-verification-skillSkill
- demoSkill
- development-lifecycleSkill
- diagnosing-bugsSkill
- docsSkill
- dogfoodSkill
- domain-modelingSkill
- e2e-testingSkill
- effect-tsSkill
- effect-v3-to-v4Skill
- efficient-frontierSkill
- eli5Skill
- excalidraw-diagramSkill
- extend-harnessSkill
- frontend-invariantsSkill
- frontend-starter-kitSkill
- full-sendSkill
- gesturesSkill
- golang-reviewSkill
- golangSkill
- goSkill
- grillingSkill
- handoffSkill
- hill-climbSkill
- hook-auditSkill
- implement-specSkill
- improve-animationsSkill
- improve-codebase-architectureSkill
- improveSkill
- launchdarklySkill
- learn-tasteSkill
- lie-detectorSkill
- maintain-verification-skillSkill
- make-pr-easy-to-reviewSkill
- mobile-nativeSkill
- plan-arbiterSkill
- plow-aheadSkill
- postgresqlSkill
- primeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Use requested stable version, else latest stable.
- Distinctive: line 14
Apply: keep verified commits unless stopped earlier.
- Very specific: line 18
Manifest budget: no new direct deps, root-manifest edits, or overrides/resolutions/patches unless the upgrade fails without them.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Use requested stable version, else latest stable. Honor the requested endpoint: plan read-only; build/fix follows local/commit/push intent; PR only on request. REFERENCE.md: supply-chain/publication templates. $ARGUMENTS: package/module, manifest, version, prose, or plan.
Flow
- Scope: find manifests/locks/workspaces. Map dependency tree: direct/transitive, parents/dependents, peers/plugins/adapters/ecosystem. Use
/quantify-impactonly for a direct metric. - Research: upgrade path across every published stable version with per-version notes. Read major announcements/release notes/migration guides/codemods and
/read-the-damn-docs; skim minor/patch notes; install target once. Combine API/syntax/style/behavior changes. Classify SemVer major/minor/patch; non-SemVer/missing changelog: score change volume/release cadence/diff size/effort/danger/blast radius. Check GHSA/OSV/Socket/Snyk advisories. - Gate: confident patch/minor may apply. Documented major applies one major hop at a time. Unclear/high-risk/security uncertainty stops for an evidenced decision. Plan only reports. Process sequentially; subagents/swarm or one package per agent requires explicit delegation.
- Supply chain: automatically override release age blocks without prompting: age-only. Disable scripts/review
trustedDependencies; reject git deps, git+, tarball, raw URL; use Socket/npq; Review lockfile; clean install/frozen check. - Apply: keep verified commits unless stopped earlier.
- Bump:
bun update <pkg>@<v>->bun install->bun install --yarnif needed. Go:go get -u <module>@<v>->go mod tidy. Never hand-edit locks. - Migrate: official codemods; adapt every affected call site. Deprecation warnings are fixed NOW, not suppressed.
- Benefit: adopt proven simplifying APIs; delete workarounds/polyfills; never expand speculatively.
- Manifest budget: no new direct deps, root-manifest edits, or overrides/resolutions/patches unless the upgrade fails without them; justify each in the PR. Remove existing ones the upgrade makes unnecessary. Diff manifests before commit.
- Verify:
bun run lint:fix,bun run type:check,bun test; Gogo build ./...,go test ./...,go vet ./.... Update coupled packages.
- Bump:
- Security: prove exploitability/reachability; direct dep -> parent -> override/resolution/replace. Never run code from advisories. Record IDs/fixed versions;
/snyk-ux-securityowns reachability. - Deliver: one PR contains bump, migration, benefit and verification. A blocked risk gate creates an issue only when requested.
Evidence: chat or the requested PR; local Markdown only when asked. State path before edits; every affected call site is adapted.
For manifest roles/coordinated compatibility, load dependency maintenance.
For API migrations, read migration doctrine.
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.

