session-close
/session-close
End a session under token/iteration limits: write handoff, session log, memory, and teach notes as markdown into the Obsidian personal vault Work/{project}/. Use when session ends, budget hit, user says handoff/close session, or rem-ralph finishes.
- Author
- RemGrace ↗
- Repository
- rem-sdlc ↗
- Licence
- MIT
- Last repository change
- 05.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
End a session under token/iteration limits: write handoff, session log, memory, and teach notes as markdown into the Obsidian personal vault Work/{project}/. Use when session ends, budget hit, user says handoff/close session, or rem-ralph finishes.
Original author description
End a session under token/iteration limits: write handoff, session log, memory, and teach notes as markdown into the Obsidian personal vault Work/{project}/. Use when session ends, budget hit, user says handoff/close session, or rem-ralph finishes.
How it works
- Vault layout
- Config (/sdlc-config.md)
- Artifacts
- Redaction
- What never goes into the vault
- Process
- When to auto-invoke
- Completion criterion
SKILL.md preview
---
name: session-close
description: "End a session under token/iteration limits: write handoff, session log, memory, and teach notes as markdown into the Obsidian personal vault Work/{project}/. Use when session ends, budget hit, user says handoff/close session, or rem-ralph finishes."
disable-model-invocation: true
---
# Session close → Obsidian vault
When a session ends (user asks, Ralph budget hit, or soft token limit), persist four markdown artifacts into the user's **personal Obsidian repo** so the next agent/human can continue.
## Vault layout
Configured root (clone of https://github.com/RemGrace/obsidian-personal or local path):
```text
{vault}/Work/{project-name}/
handoff/{timestamp}.md
session/{timestamp}.md
memory/{timestamp}.md
teach/{timestamp}.md
```
- **timestamp:** `yyyy-MM-dd-HHmmss` (local) or ISO compact.
- **project-name:** `session.vault.project_name` or git remote name or workspace folder name (slug: lowercase, `-`).
## Config (`_/sdlc-config.md`)
```yaml
session:
max_tokens: 200000 # soft budget; null = unlimited
max_iterations: 20 # rem-ralph default
warn_tokens_ratio: 0.8
on_limit: handoff # handoff | stop | ask
vault:
path: null # e.g. C:/Users/you/obsidian-personal
# path may also be a git URL; clone to session.vault.clone_dir if missing
clone_dir: null # default: ~/vaults/obsidian-personal
remote: https://github.com/RemGrace/obsidian-personal
work_root: Work
project_name: null
git_commit: false # true → commit after write
git_push: false # true → push (requires explicit user trust)
```
Resolve vault path order:
1. `session.vault.path` if set and exists
2. `session.vault.clone_dir` if repo present
3. Clone `session.vault.remote` into `clone_dir` **only with user confirmation**
4. Else ask user for local vault path
## Artifacts
### 1. `handoff/{ts}.md`
For the **next agent** (fresh context):
- Goal / ticket / branch
- Shared understanding (from grill)
- Done / in progress / blocked
- Exact next commands (`/rem-sdlc:…`, skills)
- Pointers to tracks, plans, PRs (no secrets)
- Suggested skills
### 2. `session/{ts}.md`
**Session log** (audit):
- host agent family + model if known
- started/ended, iteration count, token estimate vs `max_tokens`
- peers used (judge/rem-ralph)
- files/commits touched (paths only)
- limits hit?
### 3. `memory/{ts}.md`
**Durable project memory** (for future sessions):
- Decisions & rationale
- Domain terms
- Operational gotchas (build commands, flakes)
- Open questions
Prefer merging new bullets; don't dump raw chat.
### 4. `teach/{ts}.md`
**Teach notes** — what the human/agent learned this session:
- Patterns that worked / failed
- Prompt or process tweaks
- Links to skills to practice
If the **`teach`** skill from mattpocock is installed, align structure with it; otherwise use the sections above.
## Redaction
Never write: API keys, tokens, passwords, `.env`, credentials.json, private URLs with secrets, personal data.
## What never goes into the vault
The vault is a **text** archive. Copy markdown, and only the screenshots a report actually needs.
- **No video.** `*.webm`, `*.mp4`, `*.mov` — demo recordings stay where the cycle wrote them
(`_/recordings/`). Reference them by filename in the session log or handoff instead:
`demo: _/recordings/<TICKET>.<run-id>.webm (local)`.
- No other binaries either: archives, dumps, build output, node_modules.
Why: a handful of recordings outweighs years of notes. 62 demos once turned a markdown vault into a
242 MB repo, and git keeps every byte forever — a video deleted later still bloats history.
## Process
1. Read config + resolve vault + project-name.
2. Create directories under `Work/{project}/…`.
3. Write the four files (same timestamp).
4. Optionally update a thin index `Work/{project}/README.md` with latest links.
5. If `git_commit: true`: commit only those paths with message `memory({project}): session {ts}`.
6. Push only if `git_push: true` **and** user confirmed this session.
7. Also keep a local copy under `_/session-close/{ts}/` for the project.
8. Report absolute vault paths to the user.
## When to auto-invoke
- `session.on_limit: handoff` and token/iteration budget reached (Ralph or long cycle)
- User: "close session", "handoff", "save to obsidian"
- End of successful `/rem-sdlc:cycle` if `session.close_on_cycle_end: true`
## Completion criterion
- [ ] Four markdown files exist under the vault paths (or user declined vault → only `_/session-close/`)
- [ ] No secrets in content
- [ ] No video or other binaries copied into the vault
- [ ] User told next exact step for the following session
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · RemGrace/rem-sdlc | 100 | MIT |
| dedujeong/gemba | 100 | Apache-2.0 |
| hgbeigi/claude-tools | 100 | MIT |
| AMDResearch/omniprobe | 90 | MIT |
Database snapshot: 13.11.2026 · package version f6aeb0e9a50d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100handoff
Save and resume work sessions as handoff notes in an Obsidian vault, and keep one digest note for each project there. Use for \"save this session\", \"write a handoff\", \"load my last context\" or \"what was I working on\". Not for decisions (use mip) or conventions (use AGENTS.md). - 90graph
Maintain the Obsidian activity graph (engineering vault): set up a new project folder, ingest a raw source, close a session, run the lint, pull GitHub activity, write the weekly rollup, analyse the graph, or move the vault. Use when the user mentions the graph, the vault,… - 95obsidian-tracker-session-log
Log current session to Obsidian project. Use when the user invokes /session-log. - 90session-log
At the end of a work session, record decisions, learnings, measurable impact and next steps in the project's docs and, if configured, the user's Obsidian vault. Use when the user says "wrap up", "log this session" or runs /alexis:session-log. - 100setup
Connect the current project to a folder in an Obsidian vault so every Claude Code session gets an automatic note and every new session starts with a brief. Use when the user asks to set up vault-notes, connect Obsidian, stop re-explaining the project between sessions, or… - 100obsidian-wiki
Use the user's Obsidian vault as the agent's long-term memory: recall what is already known BEFORE answering, write session conclusions back as indexed notes, and keep the wiki consistent across sessions. Fires on 「我之前记过吗」「vault 里有什么」「我们当初怎么决定的」, on any question the user's own…