メニュー
Coalesce commits since the last git tag into a ChangeLog entry following the project's strict rules (4 sections, terse, no commit IDs, no trivial fixes). Use when the user says "update the ChangeLog" or as a step of /version-bump.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | changelog-update |
| description | Coalesce commits since the last git tag into a ChangeLog entry following the project's strict rules (4 sections, terse, no commit IDs, no trivial fixes). Use when the user says "update the ChangeLog" or as a step of /version-bump. |
The ChangeLog file lives at repo root. Per CLAUDE.md, it has very specific rules — they exist because the ChangeLog targets emulator users, not developers, and is NOT an exhaustive change log.
v0.92.0). If unknown / not bumping, use (current date) per CLAUDE.md fallback.YYYY-MM-DD form.git log --oneline <last-tag>..HEAD
git log --stat <last-tag>..HEAD
Also scan handover memos since the last tag for "what this session did" sections — they're often more readable than raw commit messages.
For each commit, classify into exactly ONE section. Drop trivial commits entirely.
New things the user (= someone running games / programs) will notice. Examples:
New things a developer using jnext will notice. Examples:
Functional fixes that change behaviour for the user. Examples:
Big architectural/test/process changes the user doesn't directly see but that are worth noting. Examples:
# ChangeLog
## vX.Y.Z (YYYY-MM-DD)
### User Features
- ...
### Developer Features
- ...
### Bug Fixes
- ...
### Internal JNEXT Development
- ...
## vP.Q.R (date)
...
If no commits exist for a section, omit the section (don't leave an empty header).
git describe --tags --abbrev=0.git log --oneline <last-tag>..HEAD.ChangeLog (above the previous version's entry).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".