Agent skill

Version Bump Project

by Vilin97 in Vilin97/lean-pool

Repair a SINGLE Lean Pool project's build against a new Lean/Mathlib release.

Apache-2.0Auto-check passed

Install Version Bump Project

skills CLI
$ npx skills add Vilin97/lean-pool --skill version-bump-project -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Vilin97/lean-pool version-bump-project --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Vilin97/lean-pool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/version-bump-project .claude/skills/version-bump-project && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
version-bump-project
GitHub stars
1
Token cost
~1.2k tokens
SKILL.md length
631 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Repair a SINGLE Lean Pool project's build against a new Lean/Mathlib release.

  • Works in 5 steps: No statement drops. Every… → Change a statement only when the… → Never add sorry, admit, native_decide, a… → …
  • Asked to fix one project (not the whole pool) for a target version
  • SKILL.md covers Hard constraints (never violate), Environment, Recipe and Report
  • Calls rg and git

What it does

Version Bump Project is an agent skill from Vilin97/lean-pool. Repair a SINGLE Lean Pool project's build against a new Lean/Mathlib release. Used by the mathlib-bump workflow's repair fan-out, one job per broken project. Use when asked to fix one project (not the whole pool) for a target version.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The licence is Apache-2.0.

When your agent uses it

  • Asked to fix one project (not the whole pool) for a target version

Example prompts

  • “/version-bump-project”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. No statement drops. Every theorem/lemma/def/instance/structure/
  2. Change a statement only when the statement itself does not compile under
  3. Never add sorry, admit, native_decide, a new axiom, unsafe,
  4. Never edit .github/, python/lean_pool/quality.py, lint configs,
  5. Do not commit, push, or open a PR. The workflow captures your working

What it can do on your machine

Read from SKILL.md and the folder at commit 01db1d7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • rg
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Version Bump Project loads about 1.2k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 631 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Vilin97/lean-pool at commit 01db1d7, republished under its Apache-2.0 licence (© Vilin97). 631 words, ~1,244 tokens.

Download SKILL.mdSave it as .claude/skills/version-bump-project/SKILL.md (or your agent's skills folder).
name
version-bump-project
description
Repair a SINGLE Lean Pool project's build against a new Lean/Mathlib release. Used by the mathlib-bump workflow's repair fan-out, one job per broken project. Use when asked to fix one project (not the whole pool) for a target version.
argument-hint
<Project> <target-version> e.g. Polytopes v4.33.0-rc1

Repair one project for a new Mathlib release

Fix only LeanPool/<Project> so that lake build LeanPool.<Project> succeeds with zero errors and zero warnings under the target release. The project and version are the arguments; if either is missing, stop and say so.

This runs headless in CI with no reviewer present. The whole-pool equivalent is the version-bump skill; this is its per-project unit of work. Pool projects never import each other, so your project is independent of every other repair running in parallel — never edit outside your project's directory.

Hard constraints (never violate)

  1. No statement drops. Every theorem/lemma/def/instance/structure/ inductive/class/abbrev that exists now must still exist when you finish. A statement that Mathlib has since absorbed is still not yours to delete — leave it and note it in your summary; that call belongs to the reviewer.
  2. Change a statement only when the statement itself does not compile under the target (a renamed or removed Mathlib symbol in its type, or a name that now collides with a new Mathlib declaration). Then make the minimal meaning-preserving change — usually a rename that keeps the statement and proof intact. Everything else: change proof bodies, tactics, and syntax only. A def → theorem keyword change for a Prop-valued declaration flagged by the defProp linter is allowed (same statement).
  3. Never add sorry, admit, native_decide, a new axiom, unsafe, partial, a maxHeartbeats/maxRecDepth increase, set_option linter.* false, or any nolint waiver. Fix the code, not the check. These are enforced by python/lean_pool/quality.py on the assembled branch, so adding one does not get the bump merged — it just wastes the run.
  4. Never edit .github/, python/lean_pool/quality.py, lint configs, lakefile.toml's [leanOptions], lean-toolchain, or any file outside LeanPool/<Project>/ (and LeanPool/<Project>.lean if it exists).
  5. Do not commit, push, or open a PR. The workflow captures your working tree as a patch and assembles it. Just leave the files fixed on disk.

Environment

  • The toolchain and Mathlib cache are already installed; lake exe cache get has run. The pins are already at the target version.
  • CLI only — the lean-lsp MCP is not available. Use:
    • lake build LeanPool.<Project> to check your work (this is the ground truth)
    • lake env lean <file> to check a single file quickly
    • rg <pattern> .lake/packages/mathlib to find what a symbol was renamed to
  • diagnostics.txt in the working directory holds the exact errors this project produced during the probe build. Start there.
Show full SKILL.md (236 more words)Show less

Recipe

  1. Read diagnostics.txt and bucket the errors by root cause. Most projects fail for one or two reasons repeated many times, not N independent reasons.
  2. Identify each root cause in Mathlib. For a renamed lemma, rg the old name in .lake/packages/mathlib — deprecation aliases usually carry a Use X instead note naming the replacement. Trust the deprecation note over a guess.
  3. Apply the minimal fix across the project. Prefer a mechanical rename over a proof rewrite; prefer a proof rewrite over any signature change.
  4. Rebuild with lake build LeanPool.<Project> until there are no errors.
  5. Clear warnings too — CI fails on any warning: line. Typical sources: deprecation renames (do what the warning says), unused simp arguments, no-op or never-executed tactics, and the defProp def → theorem case.
  6. Self-check before finishing:
    • git diff — is every changed file inside your project?
    • Diff declaration names against the base revision. Anything present before and missing now is a violation of constraint 1 unless it was a forced rename you can justify.
    • git diff | rg 'sorry|admit|native_decide|maxHeartbeats|set_option linter' must be empty.

Report

Finish with a short structured summary — it is the return value, not a message to a human:

project: <Project>
status: clean | errors-remain | warnings-remain
root_causes: <one line each>
statements_modified: <qualified name + why, or "none">
absorbed_by_mathlib: <declarations that now duplicate Mathlib, or "none">
notes: <anything the reviewer must check by hand>

If you cannot get the project clean, say so plainly in status and report what remains. A partial, honest repair is useful; a green report that is not green is not. Never disable a check to make the build pass.

© Vilin97, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/version-bump-project of Vilin97/lean-pool.

Open the folder on GitHubat commit 01db1d7

Compare with similar skills

Version Bump Project next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Version Bump Project compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Version Bump Project this skillVilin97/lean-pool1—~1.2kAutomated safety check: PassApache-2.0
Bump Dartflutter/flutter180k—~1.2kAutomated safety check: PassBSD-3-Clause
Openclaw Repair Sweepopenclaw/openclaw392k—~1.8kAutomated safety check: PassMIT
TDD Repairruvnet/ruflo74k—~1.6kAutomated safety check: NotesMIT
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Lean Formalizewanshuiyin/Auto-claude-code-research-in-sleep17k—~5.4kAutomated safety check: NotesMIT

Similar skills

  • Bump Dart

    flutter/flutter

    Do not trigger automatically; only run when a user runs /bump-dart.

    180k GitHub stars~1.2k tokensUpdated today
    MobileAuto-check passed
  • Openclaw Repair Sweep

    openclaw/openclaw

    Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

    392k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed
  • TDD Repair

    ruvnet/ruflo

    Test-Driven Repair — given a failing test, spawn a bounded headless claude -p (Read/Edit/Bash only) that makes the test pass without modifying it.

    74k GitHub stars~1.6k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • Lean Formalize

    wanshuiyin/Auto-claude-code-research-in-sleep

    Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement.

    17k GitHub stars~5.4k tokensUpdated 4 days ago
    Auto-check: notes
  • Plugin Version Bump and Release

    thedotmack/claude-mem

    Runs a semantic-versioning release workflow for a Claude Code plugin: bumps every manifest, builds, tags, creates a GitHub release, generates a changelog and publishes to npm.

    99k GitHub stars~1.7k tokensUpdated 2 days ago
    DevelopmentAuto-check: warnings

More from Vilin97/lean-pool

  • Version Bump

    Vilin97/lean-pool

    Migrate the entire Lean Pool to a new Lean/Mathlib version — bump the toolchain + Mathlib + docbuild pins, repair every project's API breakage and build warnings, pass all CI gates, and open a…

    1 GitHub stars~1.9k tokensUpdated 4 days ago
    Auto-check passed

Questions about Version Bump Project

What does Version Bump Project do?

Repair a SINGLE Lean Pool project's build against a new Lean/Mathlib release. Version Bump Project is an agent skill from Vilin97/lean-pool. Repair a SINGLE Lean Pool project's build against a new Lean/Mathlib release.

When should I use Version Bump Project?

Version Bump Project fits situations like: asked to fix one project (not the whole pool) for a target version.

How do I install Version Bump Project in Claude Code?

Run `npx skills add Vilin97/lean-pool --skill version-bump-project -a claude-code`. Or copy the skill folder (.claude/skills/version-bump-project in Vilin97/lean-pool) into .claude/skills/version-bump-project in your project. Claude Code loads it when a task matches its description.

How do I install Version Bump Project in Codex?

Run `npx skills add Vilin97/lean-pool --skill version-bump-project -a codex`. Or copy the skill folder (.claude/skills/version-bump-project in Vilin97/lean-pool) into .agents/skills/version-bump-project in your project. Codex loads it when a task matches its description.

Can I use Version Bump Project in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Vilin97/lean-pool --skill version-bump-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/version-bump-project, .gemini/skills/version-bump-project, .github/skills/version-bump-project and .opencode/skills/version-bump-project in your project.

What does Version Bump Project need to run?

Going by SKILL.md and its folder, Version Bump Project needs the command-line tools its instructions call (rg and git).

Does Version Bump Project access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Version Bump Project safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Version Bump Project use?

Version Bump Project is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Version Bump Project use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Version Bump Project?

Skills that share tags, products or a category with Version Bump Project: Bump Dart (flutter/flutter, 180k stars), Openclaw Repair Sweep (openclaw/openclaw, 392k stars), TDD Repair (ruvnet/ruflo, 74k stars) and Release Bump (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Version Bump Project?

Vilin97 (a GitHub user) maintains it in Vilin97/lean-pool, which has 1 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

Source: Vilin97/lean-pool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.