← ClaudeAtlas

end-sessionlisted

End-of-session close-out routine. The user's agreed command to wrap up a work session correctly and losslessly. TRIGGER when the user types /end-session, or says 'סוף סשן', 'סיימנו', 'תסגור סשן', 'נגמר הסשן', 'סוגרים', 'end session', 'wrap up', 'close out the session'. Runs the full ordered close-out: external-changes safety check → primer → journal → changelog → version bump → registry commit+push (verified) → Layer-4 memory. Skip individual steps per the per-step skip rules. NEVER trigger mid-task — only when the user signals the session is done.
hiyabh/claude-end-session-skill · ★ 0 · Code & Development · score 54
Install: claude install-skill hiyabh/claude-end-session-skill
# End Session — Agreed Close-Out Command ## Purpose One agreed command (`/end-session`) that runs the complete, ordered end-of-session routine so **zero context is lost** and all persistent stores stay in sync. This consolidates Iron Rule #3 (docs auto-update), the 5-Layer Memory protocol, the Session Journal, the Global Project Registry, and the CHANGELOG rules into a single deterministic sequence — plus the agreed safety/verification additions. **Trigger model:** user-invoked only. The user types the command (or an equivalent Hebrew phrase) when *they* decide the session is over. This is NOT a Stop hook and must NOT fire automatically mid-task. **Language:** all explanations/summaries to the user in Hebrew. Code, commit messages, and file content per the global formatting rules. --- ## Pre-flight (run first, before any write) **P0. Confirm scope.** If the session was read-only / research-only with **zero file changes and zero project work**, do NOT run the full routine. Say so in Hebrew and stop. (A pure-question session does not need a journal, registry row, or changelog.) **P1. Determine the active project.** - Identify which project folder this session actually worked on (`C:\Users\hiya\Documents\<project>\` or another path). - The workspace `claude-general` is **not a git repo** and is for cross-cutting experiments — for it, steps 3 (changelog), 5 (version bump), and the in-project git parts of step 4 are normally **N/A**; only the registry repo gets commit