// Use when bumping version, creating a release tag, or pushing a version tag. Triggers on "version up", "release", "tag push", "bump version".
Regenerate the Starlight website's capture PNGs (hero / agent-pane-focus / activity-focus / git-focus / worktree-spawn / og-image) from the tmux scenario fixtures. Trigger on "regenerate captures", "rebuild capture images", "update hero image", "update agent pane image", "再生成 画像", "キャプチャ更新", and any request that changes `fixtures/scenarios/**` or the seeding logic in `_lib.sh`.
Investigate whether the latest hook events and features from Claude Code / Codex CLI are covered by tmux-agent-sidebar's current implementation, and report gaps. Use on requests like "check diff with upstream", "look for new hooks", "check changelog for unsupported features". Does not implement anything.
Audit docs/ design documents, specs, and implementation plans against current source code for drift. Outputs a drift report and updates documents. Triggers on "check if docs are up to date", "diff docs vs code", "update design docs", "docs consistency check", "verify specs match source", "check plan completion status". Most effective after code or documentation changes.
Display all agent pane UI elements simultaneously in the sidebar for visual verification. Trigger on "UI check", "showcase", "UI demo", "show all patterns", "verify panel display", "UIを確認したい", "showcaseして". Use after UI changes to visually confirm rendering.
| name | version-release |
| description | Use when bumping version, creating a release tag, or pushing a version tag. Triggers on "version up", "release", "tag push", "bump version". |
Workflow for updating the version in Cargo.toml, creating a git tag, and pushing it.
grep '^version' Cargo.toml.git describe --tags --abbrev=0 --match 'v*'git log <prev-tag>..HEAD --onelinepatch / minor / major, and present the proposed version number to the user before editing any files. Do not skip this step even for a single commit — the user should always see the commit range and the classification you used.version field in Cargo.toml using the Edit tool..claude-plugin/plugin.json and update its version field to the same value. The two MUST stay in lockstep — tests/plugin_hooks_tests.rs enforces this. Without bumping plugin.json, users who installed via /plugin install will not see the new release because Claude Code uses this field for update detection.cargo check to update Cargo.lockcargo fmt --check && cargo clippy && cargo testCargo.toml, Cargo.lock, and .claude-plugin/plugin.json (message example: Bump version to X.Y.Z)git tag vX.Y.Z && git push && git push origin vX.Y.ZThis project is still pre-1.0, so SemVer is relaxed: the major stays at 0
and breaking changes ride on minor bumps.
| Signal in commit range | Bump | Example |
|---|---|---|
Any feat: / new user-visible behavior / breaking change | minor | 0.5.2 → 0.6.0 |
Only fix: / refactor: / chore: / docs: / test-only | patch | 0.5.2 → 0.5.3 |
Post-1.0 only: breaking change (feat!:, BREAKING CHANGE footer) | major | 1.x → 2.0.0 |
Rules of thumb when classifying:
feat: commit as a minor bump trigger, even if the rest are fixes.| Bump type | Example |
|---|---|
| patch | 0.2.0 → 0.2.1 |
| minor | 0.2.0 → 0.3.0 |
| major | 0.2.0 → 1.0.0 |
v prefix (e.g., v0.2.0)Cargo.lock together with Cargo.toml