wrap-session
Skill1 starsChanged 4 months agoMITView on GitHub
Use when a Claude Code session is ending and the user wants to preserve context before /clear, or wants to add session logging to a new project.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- nmamano/isomuxtheir own version, first seen Nov 7, 2026
- labsiqbal/wrap-sessiontheir own version, first seen Aug 31, 2026
- DanielOnPurpose/danielonpurpose-skillstheir own version, first seen Jul 27, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- nmamano/isomux★ 43same name
- DanielOnPurpose/danielonpurpose-skills★ 0same name
- labsiqbal/wrap-session★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Write session log: - create sessions/YYYY-MM-DD-NNN.md with a self-assessed confidence rating (high/medium/low, consumed by /unwrap), then …
- Very specific: line 21
Overwrite living state doc: - update _state.md atomically (tmp file, verify, rename)
- Distinctive: line 23
Append to decision log: - only if new cross-session structural decisions were made this session
- Very specific: line 64
All other instructions in wrap.md are path-agnostic.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
wrap-session
Prevents session history loss when users type /clear. Sets up a project-local /wrap slash command, or executes the wrap directly if the project already has the logging structure.
When to Use
- User says "wrap up", "log this session", "save before clear", or types
/wrap - User wants to set up session logging in a new project
- Project has a
_state.md/sessions/structure but no/wrapcommand yet
What /wrap Does
- Pre-flight check - warn before wrapping if 20+ uncommitted file deletions
- Determine session ID - scan
sessions/for today's files, increment to nextYYYY-MM-DD-NNN - Write session log - create
sessions/YYYY-MM-DD-NNN.mdwith a self-assessedconfidencerating (high/medium/low, consumed by/unwrap), then append tosessions/_index.jsonl - Overwrite living state doc - update
_state.mdatomically (tmp file, verify, rename) - Consume the change-ledger - summarize hook-captured file changes while their content is still in context, then clear the ledger
- Append to decision log - only if new cross-session structural decisions were made this session
- Update CLAUDE.md breadcrumb - sanitized sentinel block pointing at the new session
- Report - output
Session logged as \<id>`. Safe to /clear.`
Three-Document System
| File | Purpose | Update pattern |
_state.md | Current project health, open items, user preferences | Overwritten each session |
_decisions.md | Locked-in cross-session decisions | Append-only - never delete |
sessions/YYYY-MM-DD-NNN.md | Full session detail | Created once, immutable after |
Setting Up in a New Project
Step 1 - Create the logging structure
<logs-dir>/
_state.md # Living doc - overwritten each session
_decisions.md # Append-only decision log
sessions/
(empty - Claude fills this)Seed _state.md with current project state. Seed _decisions.md with the header only.
Step 2 - Create the /wrap command
mkdir -p .claude/commandsCopy wrap.md from this skill into .claude/commands/wrap.md.
Adapt the three path comments at the top of the copied file:
<!-- SESSIONS_DIR: logs/sessions -->
<!-- STATE_DOC: logs/_state.md -->
<!-- DECISIONS_LOG: logs/_decisions.md -->All other instructions in wrap.md are path-agnostic.
Step 3 - Invoke
/wrapor
/project:wrapSession Log Frontmatter
---
schema_version: 2
session_date: YYYY-MM-DD
session_id: YYYY-MM-DD-NNN
summary: one-line description
confidence: high # high|medium|low - self-assessed context completeness, see the rubric in wrap.md
status: complete
tags: [session]
files_changed: 0
open_items: 0
---Common Mistakes
| Mistake | Fix |
/wrap not found | File must be at .claude/commands/wrap.md, not .claude/wrap.md |
| Session ID collision | Always scan existing files before picking ID - never hardcode |
_state.md not updated | Step 3 must overwrite, not append |
| Decision log bloated | Only append when a genuine cross-session structural decision was made |
Wrap run after /clear | Too late - context is gone. Always /wrap before /clear |
Two sessions /wrap at once | IDs are scan-then-write - parallel wraps can collide on the same NNN. Run one at a time |
| Wrong paths in wrap.md | Adapt the three path comments at the top of wrap.md to match your project |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

