jnext

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".

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.

List all project-local skills, subagents, and reference docs for the jnext repo with one-line descriptions. Use when the user says "what skills do I have", "list commands", "what's available", "what can you do here", or asks to discover the project's .claude/ inventory.

Produce an end-of-session jnext handover memo in the project's established format (branch, HEAD, commits-ahead, test triplet, next-session priorities) and save it as an auto-memory entry. Use when the user says "prepare for handover", "prepare for session handover", "EOD", or similar.

Run the full jnext test triplet (ctest unit-tests + FUSE Z80 opcodes + screenshot regression) and cache the result. Use when the user says "run the triplet", "full tests", "test everything", "run all tests", or asks for a comprehensive test status before committing/merging/version-bump.

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".

Look up authoritative ZX Next FPGA hardware behavior in the VHDL source at /home/jorgegv/src/spectrum/ZX_Spectrum_Next_FPGA/cores/zxnext/src/. Use when the user asks "what does the VHDL say about X", "look up VHDL for X", "what's the spec for register/port/NEXTREG X", or any time hardware-spec authority is needed before writing/fixing emulator code or tests.