| name | version-bump |
| description | Version Bump |
| disable-model-invocation | true |
Handle version bumps after changesets are ready. This command runs changeset version, syncs Cargo.toml, and updates the What's New translations.
First, run the changeset version command to apply pending changesets:
pnpm changeset version
This will:
After changeset version completes, run the version bump script to sync versions and generate What's New content:
bun scripts/version-bump.ts --generate-whats-new
This will:
apps/desktop/package.json version to apps/desktop/src-tauri/Cargo.tomlapps/desktop/src/locales/en.jsonThe generated content needs manual curation. The What's New dialog is for casual users who just want to know what changed for them. Review and edit apps/desktop/src/locales/en.json:
REMOVE entries that are too technical or irrelevant to casual users:
KEEP and REWRITE entries to be user-friendly:
Rewriting guidelines:
Example transformations:
| Generated (too technical) | Rewritten (user-friendly) |
|---|---|
| "Refactor mod installation state machine" | REMOVE (no user-visible change) |
| "Fix race condition in VPK extraction" | "Fixed mods sometimes failing to install" |
| "Add retry logic to GameBanana API calls" | "Improved reliability when browsing mods" |
| "Migrate auth to Better Auth v2" | REMOVE (no user-visible change) |
| "Add crosshair preview in settings" | "Added crosshair preview in settings" |
| "Optimize mod list rendering performance" | "Mod list loads faster" |
Confirm versions are in sync:
echo "Package.json:" && grep '"version"' apps/desktop/package.json | head -1
echo "Cargo.toml:" && grep '^version = ' apps/desktop/src-tauri/Cargo.toml
Ensure code quality:
pnpm lint:fix
pnpm format:fix
Stage all version-related changes:
git add -A
Then use the /commit command or commit manually with:
chore(desktop): bump version to X.X.X
To preview changes without modifying files:
bun scripts/version-bump.ts --generate-whats-new --dry-run
If automatic generation doesn't produce good results, manually add an entry to apps/desktop/src/locales/en.json:
{
"whatsNew": {
"versions": {
"X.X.X": {
"title": "Feature Title & Another Feature",
"features": [
"🔧 Description of first change",
"✨ Description of new feature",
"🐛 Bug fix description"
]
}
}
}
}
| Emoji | Usage |
|---|---|
| 🔧 | Bug fixes, configuration |
| ✨ | New features, UI improvements |
| 🔒 | Auth, security |
| 🎯 | Crosshairs |
| 🔌 | Plugins |
| 🎨 | Themes, styling |
| 📁 | Profiles, file management |
| 📥 | Downloads |
| 📦 | VPK, packaging |
| 🌐 | Localization, languages |
| 🛠️ | Developer tools |
| ⚡ | Performance |
| 🛡️ | Security |
| 🐛 | Bug fixes |
User: "version bump", "bump version", or /version-bump
Response:
pnpm changeset versionbun scripts/version-bump.ts --generate-whats-newscripts/version-bump.ts - Version sync and What's New generation scriptapps/desktop/package.json - Desktop app version source of truthapps/desktop/src-tauri/Cargo.toml - Rust version (must match package.json)apps/desktop/CHANGELOG.md - Source for What's New contentapps/desktop/src/locales/en.json - What's New translationsGenerate a changeset file describing the current PR's changes. Use when asked to "create a changeset", "add a changeset", "/changeset", or after implementing a feature/fix that needs a changelog entry. Produces a randomly named `.changeset/*.md` file with affected packages, bump type, and an 80-character-max user-facing summary.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Find deepening opportunities in a codebase, informed by the architecture docs in apps/docs/content/docs/developer-docs/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
Split React/TSX files containing multiple inlined components into separate single-responsibility files. Use when asked to "split components", "extract components", "single responsibility", "clean up component file", "too many components in one file", "component slop", or when running deslop/cleanup on React code.