Session End
Wrap up a coding session — run a right-sized end-of-session self-critique, optionally curator-verify the claims, prepend a SESSION_LOG.md entry, and print a rename + counter summary. Use before you /clear or stop for the day. Triggers on `/session-end`, "end this session", "wrap up and log what we did".
Install
npx skills add iamneilroberts/claude-skills --skill session-endgit clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/session-end ~/.claude/skills/session-endPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# End Coding Session
Wrap up the session: persist what was done, prepend a SESSION_LOG entry, and surface a session-rename suggestion.
## Phase 1 — Take stock
Analyze what was accomplished:
1. Files created/modified
2. Git changes made during the session
3. Tasks completed vs left open
While doing this, **count three things** (printed in Phase 5):
- `MEMORY_WRITES` — auto-memory file edits (`~/.claude/projects/*/memory/*.md`) + any memory-MCP save calls made this session
- `COMMIT_COUNT` — number of `git commit` invocations this session
- `SESSION_LOG_UPDATED` — true/false depending on whether Phase 4 actually wrote an entry
```bash
# Append session marker to the legacy per-session log if one exists
SESSION_FILE=$(ls -t .claude-sessions/session_*.log 2>/dev/null | head -1)
if [ -f "$SESSION_FILE" ]; then
printf '\n=== Session Summary ===\nEnded: %s\n\n' "$(date)" >> "$SESSION_FILE"
fi
# Capture git context for Phase 4
GIT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || true)
git diff --stat $(git rev-parse HEAD~1 2>/dev/null || echo HEAD) 2>/dev/null || echo "(no git changes this session)"
```
## Phase 2 — Session-close self-critique (surface gaps before you log)
**Right-size it — don't manufacture concerns.** A long-but-simple session (few files, nothing
risky, nothing shipped) gets one honest line ("nothing shaky; only X was deferred") and you're
done. Scale up only when the work was complex, touched risky surfaces (auth / payments / prod /Details
- Skill name
session-end- Repository
- iamneilroberts/claude-skills
- Path
skills/session-end/SKILL.md- Repo updated
- 21 August 2026
FAQ
What does the Session End skill do?
Wrap up a coding session — run a right-sized end-of-session self-critique, optionally curator-verify the claims, prepend a SESSION_LOG.md entry, and print a rename + counter summary. Use before you /clear or stop for the day. Triggers on `/session-end`, "end this session", "wrap up and log what we did".
How do I install the Session End skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill session-end. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Session End 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.
Session Start
37iamneilroberts/claude-skills
Begin a documented coding session — create a per-session log so progress is tracked and later wrap-up (/session-end) has something to append to. Use at the start of a work session. Triggers on `/session-start`, "start a coding session", "begin a session".
Crisp
37iamneilroberts/claude-skills
Use this skill when the user wants shorter, more direct responses. Activate on: "crisp mode", "go crisp", "/crisp", "be brief", "less tokens", "cut the fluff", "shorter answers", "stop being verbose", "drop the filler", "skip the pleasantries", "no fluff", "just the answer". Do NOT activate for: "explain in detail", "walk me through", "full report", or any question answerable correctly in one sentence without the skill.
Wechat Miniprogram
32joneqian/claude-skills-suite
WeChat Mini Program development framework. Use for building WeChat mini apps, WXML templates, WXSS styles, WXS scripting, component development, and WeChat API integration.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.