Close this chat by writing its session record — a summary of this session into its workspace's sessions/ — and folding what lasts into workspace.md. Use when asked to smart close, to wrap up or close this chat with a record, or to write a session record.
Scanned 10/2/2026
npx -y skills add diazoxide/charter --skill smart-close --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Smart Close?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/diazoxide-smart-close)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: smart-close
description: Close this chat by writing its session record — a summary of this session into its workspace's sessions/ — and folding what lasts into workspace.md. Use when asked to smart close, to wrap up or close this chat with a record, or to write a session record.
---
# Smart close
The chat is closing. Leave behind a **session record**: a summary the next chat reads to pick up
where this one stopped. A summary, never the transcript. The last command below is what closes
the tab, so run it last, once.
## 1. Review the session
Read back over this conversation. Collect, for the record:
- **Goal** — what this session set out to do.
- **Done** — what changed: files, commits, pull requests, decisions carried out.
- **Decisions** — what was decided, and why.
- **Open** — what is unfinished, blocked or still to ask.
- **How to resume** — the first thing the next chat does, and where.
Keep credentials out: name the vault a secret lives in, never its value. Done when you can write
each of the five in a few lines.
## 2. Fold what lasts into workspace.md
In a workspace, open its `workspace.md`. Move what should outlive this session into the section
it belongs to:
- a decision every later chat should act on → `## Context & decisions`;
- a term this work coined → `## Glossary`;
- a changed goal → `charter workspace vision "<the goal>"`.
Leave `## Sessions` alone; that line is charter's. At the plane root there is no `workspace.md`; a
lesson for every persona goes to `charter persona remember <persona> --shared "<fact>"`. Done when
each lasting decision, term or goal change is in its section, or there was none.
## 3. Write the record
Title it in one line. Pass the pieces this session worked in that you are not standing in, as
`--piece <repo>/<piece>`; charter reads their branches from git. The body is exactly these five
sections, in this order, each with at least one line:
```bash
charter session record --title "<one-line title>" <<'RECORD'
## Goal
<what this session set out to do>
## Done
<what changed>
## Decisions
<what was decided, and why>
## Open
<what is left; "Nothing." if nothing>
## How to resume
<the first step for the next chat>
RECORD
```
A refusal says what to fix: fix it and run the command again. Done when it prints the record's
path. Then stop: the app closes this tab. When the command says the tab will not close by
itself, tell the operator the record is written and the tab is theirs to close.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!