dependency-update
Skill110 starsChanged 3 months agoMITView on GitHub
Guide for safely updating project dependencies. Use when asked to update packages, upgrade dependencies, or check for outdated libraries.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- shino369/claude-code-personal-workspacetheir own version, first seen Nov 8, 2026
- codewhale-hq/codewhale-plugin-marketplacetheir own version, first seen Nov 8, 2026
- jars-demo/jars-skillstheir own version, first seen Oct 25, 2026
- gocronx-team/gocrontheir own version, first seen Oct 8, 2026
- dotnet/aspiretheir own version, first seen Oct 8, 2026
- lintangknitto/agent-skillstheir own version, first seen Sep 23, 2026
Used with
Projects with it also use release.
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.
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 4 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- dotnet/aspire★ 6.4ksame name
- microsoft/aspire★ 6.4ksame name
- gocronx-team/gocron★ 808same name
- codewhale-hq/codewhale-plugin-marketplace★ 5same name
- shino369/claude-code-personal-workspace★ 4same name
- turntuptechnologies-ai/skills★ 1same name
- Abdox-menara/guard-skills★ 0same name
- jars-demo/jars-skills★ 0same name
- lintangknitto/agent-skills★ 0same name
- MrCipherSmith/goodai-base★ 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- api-designSkill
- copilot-cli-modesSkill
- debug-test-failuresSkill
- deterministic-scriptsSkill
- imagery-provider-adaptationSkill
- release-notesSkill
- security-analysisSkill
- validation-diagnosticsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
If tests fail, investigate and fix or revert
“Common” is measured: kept by at least 6 in 10 of the 8 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 Update
Overview
A structured process for safely updating project dependencies. Updates are categorized by risk level and applied in controlled batches with verification at each step.
Key Concepts
Semantic Versioning Risk Tiers
- Patch (x.x.X): Bug fixes only. Safe to batch.
- Minor (x.X.0): New features, backward compatible. Update in small batches.
- Major (X.0.0): Breaking changes. Update one at a time. Read the changelog.
Patterns & Techniques
Safe Update Process
Step 1: Audit
# Python
pip list --outdated
# JavaScript
npm outdatedStep 2: Categorize — Group by risk tier (patch, minor, major).
Step 3: Update per batch
- Update the dependency
cd hastelib && hatch build -t wheel— check buildcd hastelib && hatch run test:pytest— check behaviorcd ui && npm run lint— check for new warnings- If tests fail, investigate and fix or revert
Step 4: Security check — Scan for known vulnerabilities.
Step 5: Commit — One commit per logical group:
chore(deps): update [package] from vX to vYDecision Framework
| Update Type | Risk | Strategy |
| Patch | Low | Batch all, update together |
| Minor (well-known pkg) | Low-Med | Small batches of 3-5 |
| Minor (niche pkg) | Medium | One at a time, check changelog |
| Major | High | One at a time, read migration guide |
| Security fix | Critical | Update immediately, regardless of type |
Common Pitfalls
- Updating everything at once — If tests fail, you can't tell which update caused it
- Skipping the changelog — Major updates often require code changes
- Ignoring transitive dependencies — A safe direct dep can pull in a vulnerable transitive dep
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.