upgrade-tools
Skill13 starsChanged yesterdayMITView on GitHub
Upgrade one repo's mise tools, uv deps, Actions, and images to latest stable.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- fmind/dotfilesword for word, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 1
- fmind/dotfiles★ 13100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository62 other files it gives its agents.
- AGENTS.mdAGENTS.md
- dot_agents/AGENTS.mdAGENTS.md
- skills/repository-docs/references/agents.mdAGENTS.md
- claudeCLAUDE.md
- chezmoiSkill
- dot-developmentSkill
- dot-releaseSkill
- dot-skillsSkill
- acliSkill
- agent-frameworksSkill
- agent-harnessesSkill
- agent-projectSkill
- agent-protocolsSkill
- agySkill
- airflowSkill
- auth-statusSkill
- awsSkill
- bfSkill
- cfSkill
- chrome-devtoolsSkill
- clipboardSkill
- cloud-runSkill
- code-securitySkill
- colabSkill
- databricksSkill
- diagrams-as-codeSkill
- dockerSkill
- documentation-siteSkill
- dot-cliSkill
- draft-docSkill
- draft-mailSkill
- draft-typst-deckSkill
- duckdbSkill
- fmindSkill
- full-reviewSkill
- gcloudSkill
- ghSkill
- git-deliverySkill
- github-actionsSkill
- gwsSkill
- hfSkill
- humanizeSkill
- infra-as-codeSkill
- kaggleSkill
- kubernetesSkill
- miseSkill
- model-providersSkill
- playwrightSkill
- project-scaffoldingSkill
- pupSkill
- python-mlopsSkill
- python-stackSkill
- python-webSkill
- repository-docsSkill
- scheduled-jobsSkill
- skillifySkill
- <name>Skill
- task-promptsSkill
- terms-reviewSkill
- trimSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Keep lockfiles authoritative: commit mise.lock, uv.lock, and .terraform.lock.hcl, and pin Actions by 40-hex SHA and images by @sha256: …
- Distinctive: line 36
Document held pins: keep inline comments explaining every below-latest hold (ABI limits, broken upstream assets) and re-verify on each pass.
≈ “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
Upgrade Tools
Upgrade a single repository's tools and dependencies to latest stable releases in dependency order, gating each layer (playbook owns commands; mise owns pin rules).
Workflow
- Scope to one repository (default
.): never bump another repo unless the user gives an explicit list, canonicalizing paths/worktrees and qualifying each independently. - Separate read-only audits from upgrades: disk/drift audits inspect declarations, locks, backends, and installed versions (including
.git-less restored folders) without resolving or installing anything. - Require a green baseline: pass
mise run checkandmise run testbefore bumping (isolate dirty trees via git-worktree; stop and report if baseline is red). - Upgrade in layer order, stopping to diagnose on any failure and restoring prior pins if unqualified:
- mise:
mise run upgrade(ormise run lock:tool TOOL...) infmind/dot; exact stable pins per tool-versions.md elsewhere. - Python:
pyproject.tomlanduv.lockper playbook.md. - Infra & images: OpenTofu providers and OCI base/fixture digests.
- CI & formatters: GitHub Actions SHAs and
dprintplugins.
- mise:
- Verify the final candidate: pass the full gate and runtime smoke checks (
lefthook run pre-commit --all-filesonly in an isolated snapshot if the source tree is dirty). - Commit per ecosystem on request:
chore(deps): upgrade <ecosystem> to latestwith its lockfile (splitmise run upgradecommits by lockfile) per commit messages. - Report and preview cleanup: list old → new versions, held exceptions, gate results, and dry-run prune previews (playbook.md); deleting installs requires separate authority.
Gotchas
- Stable releases only: skip RCs, betas, and pre-releases; keep
pyproject.tomlranges distinct from exactmise.tomlpins. - Keep lockfiles authoritative: commit
mise.lock,uv.lock, and.terraform.lock.hcl, and pin Actions by 40-hex SHA and images by@sha256:digest. - Isolate breaking majors:
uv lock --upgradecan cross majors within open constraints; review lock diffs and split breaking migrations. - Document held pins: keep inline comments explaining every below-latest hold (ABI limits, broken upstream assets) and re-verify on each pass.
- Check release notes for behavior shifts: e.g.
betterleaks1.10 ignoring.betterleaks.tomlwithout--configor--unsafe-auto-load-config(betterleaks). - Check upstream READMEs for in-place successors:
isArchivedandmise registrymiss unarchived handoffs (actionlint→jactionlint,gitleaks→betterleaks).
Documentation
- mise upgrade · uv upgrading · OpenTofu lockfile · dprint update
- Releases: mise · uv · OpenTofu · dprint
- Companions: mise, dependabot, full-review.
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.

