session-close

Generates a resume-focused re-entry prompt summarizing session context for later continuation.

3|Updated Oct 28, 2020
One-click install
npx skills add https://github.com/k0d3x8its/dotfiles --skill session-close-k0d3x8its
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-close
Source: https://github.com/k0d3x8its/dotfiles/tree/main/claude/.claude/skills/session-close
Command: npx skills add https://github.com/k0d3x8its/dotfiles --skill session-close-k0d3x8its

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you end a work session without major architectural decisions, you lose context about what you were doing, where you stopped, and what remains open. This Skill closes a session cleanly and produces a concise re-entry prompt so your next session starts with full working context. ## Core Features & Use Cases - Resume Re-Entry Prompt: Emits a structured block capturing what you were working on, where you left off, and open items discovered during the session. - Lightweight TODOS Sync: Appends new open items to TODOS.md and removes completed ones, supporting both flat-format and .work/plan-based planning layouts. - Triage Refresh: Runs update-triage for logs under ~/dev/ so the next session's triage block stays current. - Use Case: You finished a debugging pass for the day with no big decisions made. Trigger /close, receive a saved re-entry prompt in /tmp, and paste it into a fresh session tomorrow to pick up exactly where you stopped. ## Quick Start Ask the assistant to run /close to end the current session and generate a resume re-entry prompt for the next session.

Frequently Asked Questions about session-close

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I close a Claude Code session and resume later?▼

Trigger /close to end the session and receive a resume re-entry prompt summarizing your focus, stopping point, and open items. The prompt is saved to a timestamped file in /tmp, and you paste it into a new session to continue.

What is the difference between /close, /checkpoint, and /handoff?▼

/close is a lightweight close that emits only a re-entry prompt with no SESSION-LOG narrative. /checkpoint is a durable end-of-work-session close with full narrative, and /handoff forks a tangent off a still-alive main session.

When should I use /close instead of /checkpoint?▼

Use /close when wrapping up without major architectural decisions worth narrating. If the session produced real decisions that belong in a SESSION-LOG, use /checkpoint instead, since /close deliberately writes no narrative.

Does session-close update my TODOS.md file?▼

Yes, it appends new open items discovered during the session and removes completed ones. It detects your planning format first, syncing either the flat TODOS.md or the .work/plan index with detail files.

Where is the resume re-entry prompt saved?▼

The prompt is written to a timestamped file at /tmp/close-{timestamp}.md and also printed to the terminal. You open a new session and paste the prompt to restore full working context.