Menú
Bump the app version in Cargo.toml after a release to start the next dev cycle
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
Experimental protocol for Deep Cuts research, prototypes, model evaluations, threshold tuning, ablations, metric comparisons, and claims about accuracy or quality. Use before running or interpreting experiments so bots preserve train/validation/test boundaries, avoid leakage, compare against baselines, and report results honestly.
Guidelines for creating, updating, reorganizing, and reviewing Deep Cuts documentation in the project wiki, including page taxonomy, lifecycle status, protected pages, proposal handling, and link verification.
Pattern for multi-agent collaboration sessions in the deep-cuts fam — forge-first coordination over the botfam substrate (Gitea issues/PRs as the coordination plane, the unified `botfam wait` wake loop, bare-actor worktrees), with IRC opt-in for design sprints, plus session-log conventions
Draft, structure, and finalize a Deep Cuts blog-series post so it conforms to the post template, house voice, and cross-post link rules. Use when writing, drafting, assembling, or editing a "Deep Cuts" blog post (the rlupi.com series), preparing a post for publishing, or adding front matter to one. Covers the template, front matter schema, voice, agent crediting, and the link linter.
Checklist and guide for adding a new analysis pass to the trait-based modular pipeline
Safe pattern for adding SQLite schema migrations in the deep-cuts Rust/rusqlite_migration stack
| name | bump-dev-version |
| description | Bump the app version in Cargo.toml after a release to start the next dev cycle |
Run this after a release has shipped, to advance the version for the next development cycle.
Edit src-tauri/Cargo.toml — this is the single source of truth:
version = "0.1.7" # ← next dev version
Sync it to package.json immediately:
node scripts/sync-version.js
Commit:
git add src-tauri/Cargo.toml package.json
git commit -m "chore: bump dev version to v0.1.7"
src-tauri/tauri.conf.json has no version field — it reads from package.json at build time. No edit needed there.models/manifest.json min_app_version is not changed here — that only moves at release time (see release-build skill).npm run tauri dev and npm run tauri build, so the manual sync in step 2 is just for keeping the working tree clean before committing.