Menu
Execute the 7-step version-bump sequence from CLAUDE.md. Atomic — bails out if any step fails. Use when the user says "bump version" or "release vX".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create a fresh agent worktree under .claude/worktrees/ off an up-to-date main, with the project's hygiene rules baked in. Use when the user says "spin up a worktree", "create a worktree for agent X", "set up a worktree for branch Y", or when about to dispatch an agent that needs an isolated work area.
Run the screenshot regression test suite (33 cases) and report pass/fail/skip triplet against the baseline. Use when the user says "run the regression", "regression tests", "screenshot tests", or asks to confirm no rendering regressions before committing/merging.
Compare jnext vs CSpect at a specific Z80 PC using DZRP — captures regs, SP, MEM[SP..+15], and slot mapping at the same PC in both emulators and diffs the result. Use when the user says "compare jnext vs CSpect at PC X", "DZRP probe at X", "run a DZRP comparison", or describes a boot-time divergence that needs jnext-vs-CSpect diff at a specific code site.
Add an env-gated diagnostic probe at a specific code site in jnext (the JNEXT_G46B_* pattern — zero cost when env unset, logs to cpu-inst-log channel when on). Use when the user says "add a probe at X", "instrument X", "add a G46B probe", or describes wanting to log emulator state at a specific PC/port/NEXTREG/memory event.
Comprehensive CSpect debugging via DZRP for jnext-vs-CSpect differential investigations. Covers hardened launch lifecycle (timeout-wrapped mono + bracketing pkill), BP-spray PC-stream capture, DZRP API quirks, and when to escalate to a custom plugin. Use whenever invoking CSpect from a script, doing BP-spray differential debugging, or any G46(b) workflow that touches CSpect — including "launch cspect", "run cspect", "BP-spray", "find divergent PC", "diff jnext vs CSpect PC stream", "cspect dzrp".
Run one pass of a Task-2-style subsystem audit. Dispatches a `subsystem-auditor` agent per subsystem in scope (in parallel where possible), then dispatches independent `subsystem-reviewer` agents on each result. Use when the user says "run an audit pass" or "audit subsystem X".
| name | version-bump |
| description | Execute the 7-step version-bump sequence from CLAUDE.md. Atomic — bails out if any step fails. Use when the user says "bump version" or "release vX". |
Execute the 7-step sequence from CLAUDE.md verbatim. Each step is gated: if a step fails, stop and report, don't continue.
Ask:
patch, minor, or major.Run both:
LANG=C make unit-testbash test/00regression/regression.shBoth must report PASS for every test (SKIPs acceptable, FAILs not). If anything fails, STOP and report — bump is not possible until tests are green.
Run: perl test/refresh-traceability-matrix.pl
Commit the result if it produced changes (docs(traceability): refresh for vX.Y.Z).
Run: bash test/refresh-subsystem-status.sh
Commit the result if changed.
Open doc/DEVELOPMENT-SESSIONS.md and add a section for the upcoming version. Distill from this session's git log + handover memo if present. Per CLAUDE.md, this is a development diary — different audience than ChangeLog.
Commit.
Invoke the changelog-update skill (which handles the rules: 4 sections, terse, no commit IDs, no trivial fixes, etc.).
Commit the ChangeLog update.
Should already be committed step-by-step above. Verify clean tree.
Run: make bump-<bump_type> where bump_type ∈ {patch, minor, major}.
This will:
version.yamlDo NOT push the tag. Per CLAUDE.md, pushes require explicit user authorization. Print the new tag and stop.
## Version bumped: vX.Y.Z
### Steps
- [✓] Tests passed (ctest N/N, regression P/F/S)
- [✓] Traceability matrix refreshed (commit <sha>)
- [✓] Unit-test status refreshed (commit <sha>)
- [✓] DEVELOPMENT-SESSIONS updated (commit <sha>)
- [✓] ChangeLog updated (commit <sha>)
- [✓] Version bumped via make bump-<type> (commit <sha>, tag vX.Y.Z)
### Next
- NOT pushed. To push, ask the user explicitly. Then:
JNEXT_ALLOW_PUSH=1 git push origin main --tags
--no-verify. If a pre-commit hook fails, fix the root cause; don't bypass.