Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

bump-version

Étoiles3

Forks1

Mis à jour1 mai 2026 à 22:05

Bump the patch version in server/Cargo.toml or website/package.json after completing a major change. Use when the user asks to bump/release a version, or when CLAUDE.md's rule about version bumps after major changes applies.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

PlugFox

PlugFox/vixen-rs

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	bump-version
description	Bump the patch version in server/Cargo.toml or website/package.json after completing a major change. Use when the user asks to bump/release a version, or when CLAUDE.md's rule about version bumps after major changes applies.

Bump Version (Vixen)

The root CLAUDE.md requires bumping the patch version after completing a user-visible change.

Which file

Server change (anything under server/) → server/Cargo.toml, field [package].version.
Website change (anything under website/) → website/package.json, field "version".
Both → bump both independently.

Rules

Use semver patch bump by default: 0.3.12 → 0.3.13.
Bump minor (0.3.12 → 0.4.0) only if the user says "minor" or the change is a user-visible feature.
Bump major only on explicit request.
After editing Cargo.toml, run cargo check (offline is fine: SQLX_OFFLINE=true cargo check) so Cargo.lock picks up the new version.
After editing package.json, no regeneration needed (Bun doesn't pin the package itself in bun.lock).
Do not tag or push — leave that to the user.
Add a matching entry to CHANGELOG.md under [Unreleased] with the (server) / (website) / (infra) tag.

Procedure

Read the current version.
Edit it in place with Edit (preserve exact formatting — the TOML is taplo-formatted).
For Cargo, run cd server && SQLX_OFFLINE=true cargo check to refresh Cargo.lock.
Append the changelog entry (component-tagged).
Include the bump in the same commit as the feature change, or as a dedicated chore: bump server to 0.3.13 commit — ask the user which they prefer if unclear.

Plus depuis ce dépôt

même dépôt

change-impact-assessment

PlugFox/vixen-rs

Before a non-trivial change, list affected systems — DB schema, API contract, Telegram handlers, jobs, TS types, docs. Catch ripple effects upfront, not after CI fails. Use when planning a feature, migration, refactor, or any cross-module touch.

2026-05-013

code-review-self

PlugFox/vixen-rs

Self-review before push — read the diff as a reader, scan for vixen footguns (token leaks, PII, idempotency, captcha asset overwrites), run validation pipeline, no surprise files. Use before "git push", before opening a PR, or when the user says "ready to commit".

2026-05-013

commit-message

PlugFox/vixen-rs

Write a git commit message for vixen-rs following the project's Conventional Commits convention. Use when the user asks to commit, create a commit, or write a commit message.

2026-05-013

debug-systematically

PlugFox/vixen-rs

Reproduce → bisect → root cause → fix → verify. Don't speculate, don't "add more error handling" as a guess. Use when something is broken, when a test fails intermittently, when the user says "this isn't working" or "investigate why".

2026-05-013

docker-multi-stage

PlugFox/vixen-rs

Write small, fast, reproducible Dockerfiles for the vixen-rs server (Rust) and website (bun) using multi-stage builds, cache mounts, distroless/alpine runtime images, and non-root users. Use when editing server/Dockerfile, website/Dockerfile, docker-compose.yml, or when the user asks to shrink an image or speed up a Docker build.

2026-05-013

find-external-skill

PlugFox/vixen-rs

Evaluate a 3rd-party Claude skill before importing — source trust, duplicate check, rule extraction, vixen-fit. Reject vague triggers and off-scope content. Use when the user shares a skill URL, asks "should we adopt this skill", or proposes importing from a marketplace.

2026-05-013

name	bump-version
description	Bump the patch version in server/Cargo.toml or website/package.json after completing a major change. Use when the user asks to bump/release a version, or when CLAUDE.md's rule about version bumps after major changes applies.

Bump Version (Vixen)

The root CLAUDE.md requires bumping the patch version after completing a user-visible change.

Which file

Server change (anything under server/) → server/Cargo.toml, field [package].version.
Website change (anything under website/) → website/package.json, field "version".
Both → bump both independently.

Rules

Use semver patch bump by default: 0.3.12 → 0.3.13.
Bump minor (0.3.12 → 0.4.0) only if the user says "minor" or the change is a user-visible feature.
Bump major only on explicit request.
After editing Cargo.toml, run cargo check (offline is fine: SQLX_OFFLINE=true cargo check) so Cargo.lock picks up the new version.
After editing package.json, no regeneration needed (Bun doesn't pin the package itself in bun.lock).
Do not tag or push — leave that to the user.
Add a matching entry to CHANGELOG.md under [Unreleased] with the (server) / (website) / (infra) tag.

Procedure

Read the current version.
Edit it in place with Edit (preserve exact formatting — the TOML is taplo-formatted).
For Cargo, run cd server && SQLX_OFFLINE=true cargo check to refresh Cargo.lock.
Append the changelog entry (component-tagged).
Include the bump in the same commit as the feature change, or as a dedicated chore: bump server to 0.3.13 commit — ask the user which they prefer if unclear.