version
Bump the project version with SemVer - detect the version files (package.json, pyproject.toml, Cargo.toml, Expo app config, Claude Code plugin manifests and their marketplace entry...), propose the bump from the commits since the last release, update every file consistently; handles Expo native vs OTA releases.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- version
- description
- Bump the project version with SemVer - detect the version files (package.json, pyproject.toml, Cargo.toml, Expo app config, Claude Code plugin manifests and their marketplace entry...), propose the bump from the commits since the last release, update every file consistently; handles Expo native vs OTA releases.
- allowed-tools
- Bash(git status *) Bash(git log *) Bash(git diff *) Bash(git tag *) Bash(git describe *) Bash(git rev-parse *) Read Glob Grep Read(/${CLAUDE_PLUGIN_ROOT}/**)
- argument-hint
- [patch|minor|major|ota]
- disable-model-invocation
- true
02 资源文件 1
- 参考文档expo.md3.0 KB
03 SKILL.md 正文
Bump the version. Requested bump, if any: $ARGUMENTS
Follow the shared rules in ${CLAUDE_PLUGIN_ROOT}/reference/git.md.
Before step 1, create a task list (the TodoWrite tool, or TaskCreate and TaskUpdate where those are the task tools) with one entry per numbered step below, titled like the step, in order. Keep it current as you go: a step is in progress when you start it and completed when it ends. A step that does not apply, or that an argument skips, is marked completed and said in the report, never left open or removed.
1. Find the version sources
Look for, outside node_modules and virtual environments:
package.json(version), including workspace packages;pyproject.toml([project] versionor[tool.poetry] version);Cargo.toml([package] version);- Expo:
app.json,app.config.tsorapp.config.js(expo.version,runtimeVersion,extra.jsVersion); - Claude Code plugins: each
.claude-plugin/plugin.json(version), and, in a marketplace repository, the plugin's entry in.claude-plugin/marketplace.jsonat the root (plugins[].version, the entry whosesourceis the plugin's folder): the two always change together, andclaude plugin validate .reports a gap; - other files that repeat the version:
CHANGELOG.md, a version badge, table or "current version" line inREADME.md, a version line inCLAUDE.mdor in a project state file (a list of versions); - markers left for a version not yet known (such as "since 0.xx.0" in a README), when the project's
CLAUDE.mdnames one; - git tags:
git describe --tags --abbrev=0.
A repository with several versioned parts (the plugins of a marketplace, workspace packages) versions each changed part on its own: a part changed when a file of its folder changed since its last version change.
If the sources disagree with each other, show them side by side and ask which one is right before changing anything.
If an Expo app is detected, read ${CLAUDE_PLUGIN_ROOT}/skills/version/expo.md now: an Expo release is either native or OTA, and the wrong choice breaks updates for installed apps.
2. Choose the bump
The commits since the last tag (or since the last change to the version field, found with git log -L or git log -G), without merge commits and, for one part of a repository with several, only those that touch its folder, decide it:
BREAKING CHANGEortype!:→ major;feat→ minor;fix,perfand the rest → patch. Below 1.0.0, the major stays 0: a breaking change and afeatboth bump the minor, and the rest the patch. flow-board's version preview computes the same bump.
With an argument, use it; if it contradicts the commits (a patch requested over a breaking change), say so and ask. Without one, propose the computed bump with the commits that justify it, and let the owner confirm or choose another.
3. Update
- npm projects:
npm version <new> --no-git-tag-versionkeepspackage-lock.jsonin step; for other package managers, editpackage.jsonand let the lockfile follow on the next install. Never hand-edit a lockfile. - Every other source from step 1 gets the same version; a marker for a version not yet known becomes the new version.
- If the project's
CLAUDE.mdnames a script that sets the version (its files, its markers), use it rather than editing by hand, then check its report. CHANGELOG.md, if the project has one: a new section at the top in the file's existing format, listing the changes from the commits in the owner's words.- If the project's
CLAUDE.mdnames a quick or static check command (for examplescripts/check.sh --quick <plugin>), run it on each plugin or package whose CHANGELOG you just wrote, before the commit of step 4, and fix what it reports (a retired term in the new entry, a malformed entry): the pre-commit hook would otherwise refuse the release commit. Without such a command, skip this.
4. Commit and tag
Commit the version files together: chore(release): v<new> (or the repository's convention). Create the tag v<new> only if the repository already tags its releases, and make it annotated (git tag -a v<new> -m "v<new>"): git push --follow-tags sends only annotated tags. Pushing is left to /project:push.
Report
Old and new version, bump type and why, files changed, tag created or not, and for Expo which release path applies (native build or OTA update).
04 同仓库更多 Skills
reserve
Skill d'essai de la sonde, réservé à l'utilisateur. Répond par un mot fixe, sans rien faire d'autre.
recap
Récap de l'usage Claude Code en chat, d'après ccusage et les relevés de requêtes de stats-board — la discussion en cours (coût, tokens, cache, durée, temps actif, attente de ta réponse, temps API, requêtes et la plus chère, modèles, spécialistes) et la journée (coût, tokens, temps actif, temps cumulé et temps API de ce poste, par projet et par modèle, discussions actives, bloc de 5 h et son rythme, autres postes publiés dans claude-usage), ou une mission entière (manager, workers et spécialistes, retrouvés par le début de leur titre ou par les worktrees groupe-* d'un projet, avec leur temps actif sans double compte et leur temps cumulé). À utiliser sur « /stats-board:recap », « récap de l'usage », « combien m'a coûté cette discussion », « combien j'ai consommé aujourd'hui », « coût de la journée », « récap de la mission », « combien a coûté la mission », « récap du parcours », « combien a coûté le parcours ». Pas pour ouvrir le panneau de statistiques, qui passe par /ccstats.
install
Installe et initialise les plugins de la marketplace mathis-plugins choisis par l'utilisateur - choix par groupes, dépendances et prérequis, installation, réglages (Asana, partage des usages, modèle de session-tools, barre d'état) et bloc de règles dans le CLAUDE.md global ou du projet, montré avant écriture. Relançable pour ajouter ou retirer des plugins.
sync
Bring the current branch up to date with its remote, or with the default branch when asked, without losing local work - fetch, rebase or merge, autostash.
push
Finish a piece of work and push it - commit what is left, run the project's checks, confirm the end-of-session files are up to date, sync with the remote and push without force.
pr
Open a GitHub pull request for the current branch against the default branch or a given base, with a title and body written from the commits - the repository's PR template, or the plugin's (public release-notes section + internal details for reviewers).