close
End-of-session protocol — push, checkpoint, docs, story episode
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
End-of-session protocol — push, checkpoint, docs, story episode
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
| name | close |
| description | End-of-session protocol — push, checkpoint, docs, story episode |
Session closing skill. Invoke with /close at end of session.
git log --oneline origin/master..HEAD
If commits exist, push to both remotes:
git push
Find the active checkpoint (status: active in docs/checkpoints/).
Add a new session section (## Sn: with descriptive title and date).
Content for each session section:
Use the existing checkpoint sections as format reference. Be concise but complete — the checkpoint is the permanent record.
Count session headers (## S) and total lines in active checkpoint.
Rotate if ANY of:
Rotation procedure:
status: active to status: done in frontmatterdocs/checkpoints/YYYY-MM-DD-cpNN.md
with status: active, # CPNN, and Previous: line summarizing
the closed checkpoint## State at checkpoint creation with current statsdocs: close CPxx, create CPyyCheck if this session's work affects any of these docs. Only update if the content has actually changed:
docs/architecture.md — new modules, tables, activities, endpointsdocs/strategy.md — schedule changes, new cycle typesdocs/patterns.md — new patterns, changed infrastructuredocs/todo.md — already handled in step 3Skip docs that weren't affected. Don't touch docs for cosmetic reasons.
Staleness check: Grep active docs (architecture, strategy, patterns, todo) for references to renamed/removed types, tables, methods, or changed patterns from this session. Fix any stale references found. Don't touch archive docs — they're historical records.
Every session gets an episode. There is always something to say — a design decision, a debugging rabbit hole, a production surprise, a moment where the plan met reality. Even "routine" sessions have a story: why was this the priority, what was the tradeoff, what did we learn. The project story is the narrative history of the codebase. Gaps in the story are gaps in institutional memory.
Find the angle. Some sessions have obvious drama (production crashes, reverts, architectural pivots). Others need you to look harder — the small surprise that changed the approach, the assumption that turned out wrong, the thing that was harder (or easier) than expected. If nothing went wrong, write about what went right and why.
When writing:
docs/claude-lessons.mddocs/project-evolution.md header stats (generated
date, period, total commits, pace). This is mandatory every session,
not "if significant."Commit all doc changes:
docs: close session — CP update + [whatever else changed]
Push to both remotes.
Tell the human: