update-deps
Skill295 starsChanged 30 days agoMITView on GitHub
Move the pinned dependencies to their latest targets, verify, and open a pull request.
- 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
- Zmoki/zmoki-astro-startertheir own version, first seen Oct 27, 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
- stella/stella★ 274same name
- github/rust-gems★ 139same name
- gaia-harness/gaia★ 26same 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.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-integrationSkill
- codebase-designSkill
- domain-modelingSkill
- explainSkill
- frontend-designSkill
- improve-codebase-architectureSkill
- prSkill
- researchSkill
- self-reviewSkill
- shadcnSkill
- writing-for-agentsSkill
- vibestartSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Branch: Start from an up-to-date, clean main, then create deps/update-<YYYY-MM-DD>.
- Very specific: line 10
Survey: Run vp run deps. Exit 0 means every pin is at its target: report that and stop.
- Very specific: line 12
Check: Run vp check and vp run ready.
“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
Land a dependency update as one reviewed pull request. Read "Keeping dependencies current" in CONTRIBUTING.md for what a pin is and how the pin files stay in step.
- Branch. Start from an up-to-date, clean
main, then createdeps/update-<YYYY-MM-DD>. Done whengit statusis clean on the new branch. - Survey. Run
vp run deps. Exit 0 means every pin is at its target: report that and stop. Otherwise read the table; a majorbumpor a deprecated pin is where a breaking change hides. - Update. Run
vp run deps update. It moves the pins, refreshes lockfiles, goldens, and snapshots, then runsvp run ready. When a step fails, the moved pins stay in the working tree: fix the cause at the abstraction that owns it (a template, an integration, a pin rule inpackages/integrations/src/deps), then runvp run deps updateagain. Done when it printsRepository checks passed. CI verifies every stack the pins reach on the pull request. - Check. Run
vp checkandvp run ready. Done when both pass on the final tree. - Commit. One commit,
chore(deps): update pinned dependencies, authored as the configured git user with noCo-authored-bytrailer. A tool that appends one gets bypassed withgit commit-tree. - Pull request. Push the branch and run
gh pr createagainstmain. The body lists each moved pin asname: old → newwith its bump, and names every breaking change you handled and where. Done when the pull request'scicheck passes; hand its URL to the user. A failingverifyjob names the stack and ends with its log; fix the cause as in step 3.
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.