← ClaudeAtlas

end-sessionlisted

Close out a coding session — surface uncommitted work, sync status, memory banner updates, deliverables ledger, and next-session pickup hints. Project-agnostic; never auto-commits or auto-edits memory without explicit operator approval.
sanishsk/8colors-process-engine · ★ 0 · AI & Automation · score 67
Install: claude install-skill sanishsk/8colors-process-engine
# End Session A portable close-out skill. Reports state, proposes memory updates, lists deliverables, and writes the next-session pickup pointer — but **never mutates state autonomously**. Every change is surfaced for operator approval first. ## When to use Invoke at the end of a coding session, especially when: - About to close the terminal or switch projects - Reached a natural slot boundary (e.g. just merged or promoted) - Approaching context-window pressure and want a clean handoff Skip when: - The session is mid-edit on a single file and you'll resume in <5 min - The user has explicitly asked for a different close-out flow ## Procedure Run these steps **in order**. Most are sequential because later steps depend on earlier output. ### 1. Working-tree status check Run `git status` (concise) and `git diff --stat`. If there are uncommitted changes: - List the changed files (grouped by modified / new / deleted) - Ask the operator: "Commit before close, leave as WIP, or stash?" - **Do not auto-commit.** Operator decides. If clean: state "Working tree clean." ### 2. Local-vs-origin sync check Determine the upstream branch: ```bash git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null ``` If an upstream exists, run: ```bash git log @{u}..HEAD --oneline git log HEAD..@{u} --oneline ``` Report: - N commits **ahead** of upstream (list them with hashes + subjects) - N commits **behind** (list, if any) - If ahead-only: "Want to push or carry forward?" — ope