원클릭으로 Manus에서 모든 스킬 실행

handover

스타29

포크3

업데이트2026년 5월 16일 08:11

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

jorgegv

jorgegv/jnext

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Session handover

Produce the end-of-session memo and save it to memory. The format is rigid (this project has 200+ handover memory entries; consistency matters).

Inputs to gather (auto, don't ask)

Run these in parallel:

git rev-parse --abbrev-ref HEAD → current branch
git rev-parse --short HEAD and git rev-parse HEAD → commit IDs
git rev-list --count main..HEAD → commits ahead of main
git rev-list --count origin/main..HEAD → commits ahead of origin/main
git log --oneline main..HEAD → list of session commits
git status --short → working-tree state
cat .claude/last-test-triplet.txt if present → last triplet

Triplet check

If .claude/last-test-triplet.txt is missing OR older than the latest commit, ask the user whether to run the full triplet now (the regression-runner agent or /test-triplet command). If they say no, note "triplet not freshly verified" in the memo.

Memo content

Save to /home/jorgegv/.claude/projects/-home-jorgegv-src-spectrum-jnext/memory/project_session_handover_<YYYY-MM-DD><suffix>.md. Suffix is _eod, b_eod, c_eod, etc. depending on how many handovers happened today. Frontmatter:

---
name: jnext session handover <YYYY-MM-DD><suffix>
description: <one-line summary of where the session left off — branch, what was done, what's next>
type: project
---

Body sections (in this order, terse, project conventions):

State — branch, HEAD short SHA, +N vs main, +N vs origin/main, tree clean/dirty, push status (NOT pushed unless user authorized).
What this session did — bullet list, one line per significant change. Reference commit SHAs.
Test triplet — ctest N/N • FUSE 1356/1356 • regression P/F/S, with timestamp.
Discoveries / findings — anything non-obvious learned this session that future-Claude will need.
Next-session priority — concrete next step(s), specific enough to act on without re-discovery.
Outstanding — anything escalated to user, deferred, or follow-up.

Update MEMORY.md

Add a one-line index entry at the top of the "Latest session" section in /home/jorgegv/.claude/projects/-home-jorgegv-src-spectrum-jnext/memory/MEMORY.md:

- **[<file>](<file>) ← READ FIRST. <YYYY-MM-DD> EOD — <one-line state>.** <triplet>. <next-priority>.

(The "← READ FIRST" marker moves from the previous handover to this one; downgrade the previous one to "(legacy)".)

Hard rules

NEVER include Co-Authored-by lines (CLAUDE.md project rule).
Terse but insightful (CLAUDE.md). Don't write a development diary.
Don't claim a fix is shipped if the triplet didn't confirm it. Per feedback_tremendous_claims_proof, every claim needs proof; if the triplet wasn't run, say so explicitly.
Don't push. A handover is local. Mention "NOT pushed (N ahead of origin)" if commits exist.
Convert relative dates to absolute (per memory rules).

Examples to model after

Read project_g46b_v2_2026_05_11_session_handover.md and project_task2_2026_05_11_FINAL_SESSION_HANDOVER.md from memory for the exact tone, density, and structure.

이 저장소의 다른 Skills

같은 저장소

worktree-launch

jorgegv/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.

2026-07-1229

regression

jorgegv/jnext

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.

2026-07-1229

dzrp-compare

jorgegv/jnext

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.

2026-07-1129

probe-add

jorgegv/jnext

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.

2026-07-1129

cspect-debug

jorgegv/jnext

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

2026-05-1629

audit-pass

jorgegv/jnext

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

2026-05-1629

name	handover
description	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.

Session handover

Produce the end-of-session memo and save it to memory. The format is rigid (this project has 200+ handover memory entries; consistency matters).

Inputs to gather (auto, don't ask)

Run these in parallel:

git rev-parse --abbrev-ref HEAD → current branch
git rev-parse --short HEAD and git rev-parse HEAD → commit IDs
git rev-list --count main..HEAD → commits ahead of main
git rev-list --count origin/main..HEAD → commits ahead of origin/main
git log --oneline main..HEAD → list of session commits
git status --short → working-tree state
cat .claude/last-test-triplet.txt if present → last triplet

Triplet check

Memo content

---
name: jnext session handover <YYYY-MM-DD><suffix>
description: <one-line summary of where the session left off — branch, what was done, what's next>
type: project
---

Body sections (in this order, terse, project conventions):

State — branch, HEAD short SHA, +N vs main, +N vs origin/main, tree clean/dirty, push status (NOT pushed unless user authorized).
What this session did — bullet list, one line per significant change. Reference commit SHAs.
Test triplet — ctest N/N • FUSE 1356/1356 • regression P/F/S, with timestamp.
Discoveries / findings — anything non-obvious learned this session that future-Claude will need.
Next-session priority — concrete next step(s), specific enough to act on without re-discovery.
Outstanding — anything escalated to user, deferred, or follow-up.

Update MEMORY.md

Add a one-line index entry at the top of the "Latest session" section in /home/jorgegv/.claude/projects/-home-jorgegv-src-spectrum-jnext/memory/MEMORY.md:

- **[<file>](<file>) ← READ FIRST. <YYYY-MM-DD> EOD — <one-line state>.** <triplet>. <next-priority>.

(The "← READ FIRST" marker moves from the previous handover to this one; downgrade the previous one to "(legacy)".)

Hard rules

NEVER include Co-Authored-by lines (CLAUDE.md project rule).
Terse but insightful (CLAUDE.md). Don't write a development diary.
Don't claim a fix is shipped if the triplet didn't confirm it. Per feedback_tremendous_claims_proof, every claim needs proof; if the triplet wasn't run, say so explicitly.
Don't push. A handover is local. Mention "NOT pushed (N ahead of origin)" if commits exist.
Convert relative dates to absolute (per memory rules).

Examples to model after

Read project_g46b_v2_2026_05_11_session_handover.md and project_task2_2026_05_11_FINAL_SESSION_HANDOVER.md from memory for the exact tone, density, and structure.