Session Pause
Write a detailed session handoff file by hand so the next session can pick up where this one left off. Use when the context window is filling up, you're switching phases, or you're stopping for a break.
Install
npx skills add iamneilroberts/claude-skills --skill session-pausegit clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/session-pause ~/.claude/skills/session-pausePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Session Pause
Generate a detailed handoff file so a fresh session can pick up seamlessly.
## Steps
1. **Gather git state** by running these commands:
- `git rev-parse --show-toplevel` (repo root — used for repo tagging)
- `git branch --show-current`
- `git status --short`
- `git diff --stat`
- `git log --oneline -5`
2. **Summarize from session memory** — write these sections:
- **What Was Accomplished**: completed tasks with file paths
- **Decisions Made**: key decisions with rationale
- **Files Created or Modified**: table with file path, action, description
- **Remaining Work**: actionable next steps with specific file paths
- **Open Questions**: anything needing user input
3. **Determine output path**:
- Use the repo root from `git rev-parse --show-toplevel` as the base directory (resolves to the worktree root when inside a worktree)
- If `docs/summaries/` exists under that base, write there
- Otherwise create `.claude-sessions/` under that base
- Filename: `pause-{YYYY-MM-DD}-{topic-slug}.md` where topic-slug is a 2-3 word summary of the work
4. **Write the handoff file** using atomic write (write to `.tmp` then rename):Details
- Skill name
session-pause- Repository
- iamneilroberts/claude-skills
- Path
skills/session-pause/SKILL.md- Repo updated
- 21 August 2026
FAQ
What does the Session Pause skill do?
Write a detailed session handoff file by hand so the next session can pick up where this one left off. Use when the context window is filling up, you're switching phases, or you're stopping for a break.
How do I install the Session Pause skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill session-pause. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Session Pause popular?
It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.
Related skills
Brag
37iamneilroberts/claude-skills
Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write
Branch
37iamneilroberts/claude-skills
Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".
Claude Code Best Practices
37iamneilroberts/claude-skills
Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.
Sitrep
37iamneilroberts/claude-skills
Use when the user invokes /sitrep — an occasional "state of the union" re-orientation sweep. Verifies what has actually shipped versus what handoffs, specs, memory, and chat history claim shipped (across git in one or more repos, handoff docs, specs, optional chat-history/memory MCPs, and open issues), surfaces loose ends and loss-risk (unpushed commits, stale/stray worktrees & branches, unchecked plan boxes, never-closed handoff pending sections), then resets what matters next as a milestone-anchored list plus a bounded off-roadmap-drift section. Writes a report to docs/digests/ and proposes
Write Post
37iamneilroberts/claude-skills
Turn a rough brief into a blog deep-dive draft. Takes a topic or brief, gathers the relevant sources, runs one short focused interview to pin down the angle and the claims, then writes a draft to docs/posts/<date>-<slug>.md. The default output is a rich outline — a dense, factual skeleton meant to be rewritten in your own voice — not finished prose. Pass `--draft` for full prose, `--outline` to force the outline. This is the no-BS technical counterpart to `/brag` (which builds a sales/hype showcase page); reach for write-post when the goal is an accurate deep dive. Triggers on `/write-post <to
Unity Surface Preflight
40Nice-Wolf-Studio/unity-claude-skills
Use when about to touch a Unity project for the first time in a session; before editing any scene, prefab, or asset file in a Unity repo; when a status probe reports no instances; when more than one Editor may be running; when a command returns AMBIGUOUS_EDITOR, exit 6, or times out; when deciding between running something headless and driving an open Editor.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.