Agent skill

bump-version

Bump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version. Use when: user says 'bump version', 'update version', '更新版本', '版本 +1', or /bump-version

Stars 139
Forks 18

Install this agent skill to your Project

npx add-skill https://github.com/sd0xdev/sd0x-dev-flow/tree/main/skills/bump-version

SKILL.md

Bump Version

Update package.json, .claude-plugin/plugin.json, and .sd0x/install-state.json versions in sync.

Workflow

  1. Read current versions from all files
  2. Determine new version (from argument or auto-increment)
  3. Update all files to the same version
  4. Report result

Step 1: Read Current Versions

bash
grep '"version"' package.json .claude-plugin/plugin.json

Also check manifest:

bash
grep '"plugin_version"' .sd0x/install-state.json 2>/dev/null || echo "(no manifest)"

If versions are already out of sync, warn user before proceeding.

Step 2: Determine New Version

Input Action
Explicit version (e.g., 1.9.0) Use as-is
major Bump major: 1.8.12.0.0
minor Bump minor: 1.8.11.9.0
patch (default) Bump patch: 1.8.11.8.2
No argument Default to patch

Step 3: Update All Files

Use Edit tool to update version fields:

  1. package.json"version" field
  2. .claude-plugin/plugin.json"version" field
  3. .sd0x/install-state.json"plugin_version" field (if file exists)

All must be set to the exact same version string.

The manifest update prevents the SessionStart drift sentinel from firing false warnings after every version bump in the plugin source repo.

Step 4: Report

## Version Bump

| File | Field | Before | After |
|------|-------|--------|-------|
| package.json | version | x.y.z | a.b.c |
| .claude-plugin/plugin.json | version | x.y.z | a.b.c |
| .sd0x/install-state.json | plugin_version | x.y.z | a.b.c |

Prohibited

  • Never set different versions across the files
  • Never modify other fields in the JSON files

Expand your agent's capabilities with these related and highly-rated skills.

sd0xdev/sd0x-dev-flow

runbook

Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).

139 18
Explore
sd0xdev/sd0x-dev-flow

ask

Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or skills during development. Not for: code changes (use feature-dev), code review (use codex-review-fast), deep research (use deep-research), full code trace (use code-explore). Output: structured answer with source attribution.

139 18
Explore
sd0xdev/sd0x-dev-flow

project-brief

Convert a technical spec into a PM/CTO-readable executive summary. Simplify technical details, focus on business value.

139 18
Explore
sd0xdev/sd0x-dev-flow

codex-test-gen

Generate unit tests for specified functions using Codex MCP

139 18
Explore
sd0xdev/sd0x-dev-flow

bug-fix

Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore). Output: fix + regression test + review gate.

139 18
Explore
sd0xdev/sd0x-dev-flow

skill-health-check

Validate skill quality against routing, progressive loading, and verification criteria. Use when: auditing skills, checking skill health, reviewing skill design. Not for: code review (use codex-code-review) or doc review (use doc-review). Output: health report with per-skill ratings + Gate.

139 18
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results