Menú
Bump the project version across all files that carry it. Pass the new version as the argument (e.g. /bump-version 0.4.0).
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Full code navigation — replaces grep, glob, and file reads. Find symbol definitions, trace callers and callees, read source code, and map module structure. Pass symbol names or questions as arguments.
Generate a PR description as a Markdown file in .claude/scratch using git history and code analysis. Fills in the project's PR template.
Diagnose and fix a bug or unexpected behavior. Traces the problem through the dependency graph, adds logging if needed, and proposes a fix. Use when something is broken, producing wrong output, or behaving unexpectedly.
Plan implementation before writing code. Analyzes codebase structure and dependencies, asks clarifying questions, and writes a scoped implementation spec.
| name | bump-version |
| description | Bump the project version across all files that carry it. Pass the new version as the argument (e.g. /bump-version 0.4.0). |
| argument-hint | <new version> |
| allowed-tools | Read Edit Bash |
Bump the project version to $ARGUMENTS across every file listed below. For each file, search for the current version string and replace it with $ARGUMENTS.
| File | What to change |
|---|---|
pyproject.toml | version = "..." under [project] |
rust/Cargo.toml | version = "..." under [package] |
src/serpentine/__init__.py | __version__ = "..." |
frontend/package.json | "version": "..." |
apps/marketing/src/pages/index.astro | badge text v... · Apache 2.0 and CTA badge { dot: false, label: 'v...' } |
Run grep -r "OLD_VERSION" . --include="*" -l | grep -v .git with the current version to confirm no new files have been added since this skill was written. If any unexpected files appear, update them too and add them to this skill's table.
Read each file listed above, then apply the edits.
After all edits, tell the user to regenerate the lock files:
uv lock # regenerates uv.lock
cd rust && cargo update # regenerates rust/Cargo.lock (bare cargo build will fail — PyO3 needs maturin)
cd frontend && npm install # regenerates frontend/package-lock.json
uv.lock, rust/Cargo.lock, frontend/package-lock.json). They are auto-generated and contain checksums — manual edits leave them inconsistent. Let the build tools regenerate them.apps/marketing/bun.lock contains "db0": ">=0.2.1" — this is a third-party peer dependency constraint, not the project version. Do not change it.index.astro has two version references: the hero badge and the CTA badge at the bottom. Update both.