end-session
Skill1 starsChanged 5 months agoMITView on GitHub
Checkpoint the session into the second-brain — records what actually happened (git-anchored) and what is next, updates the dashboard, syncs git facts. Use before ending a working session or before /clear.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- jocarrd/crux-agentstheir own version, first seen Nov 8, 2026
- abhayla/claude-best-practicestheir own version, first seen Nov 1, 2026
- DavoDC/claude-playbooktheir own version, first seen Oct 13, 2026
- lunaman81/claude-skillstheir own version, first seen Oct 6, 2026
- edwardyen724-g/claude-session-skillstheir own version, first seen Aug 30, 2026
- jctots/thinkpad-fedora-agenttheir own version, first seen Aug 15, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- YehudaFrankel/clankbrain★ 16same name
- abhayla/claude-best-practices★ 9same name
- ozgurkarahan/ai-agent-memory★ 8same name
- alxyrgin/agent-forge★ 4same name
- jocarrd/crux-agents★ 4same name
- DavoDC/claude-playbook★ 1same name
- heffrey/claude-skills★ 1same name
- edwardyen724-g/claude-session-skills★ 0same name
- jctots/thinkpad-fedora-agent★ 0same name
- lunaman81/claude-skills★ 0same name
2 more not listed
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.
In this repository3 other files it gives its agents.
- analyzeSkill
- setupSkill
- start-sessionSkill
The file
Files
second-brain: end-session
Git-anchored write. Follow the discipline below EXACTLY — Part 1 governs this skill.
!cat "${CLAUDE_PLUGIN_ROOT}/references/discipline.md"
Steps
- Locate the vault (cwd or ancestors containing
Projects/Dashboard.md; else registered vaults in~/.claude/second-brain/vaults, ask if several; none → "run /second-brain:setup first"). - Which repo(s) were touched this session? Evidence: this conversation's work +
git -C <repo> status -sb+git -C <repo> log --oneline -10. Cannot tell → ASK the user; never guess. - For each touched repo, update
Projects/<repo>.mdper Part 1:## ▶ Thread→Last:cited facts — ALL commits since that note'slast_handoff_commit(hash+subject viagit log <last_handoff_commit>..HEAD --oneline, or the full log iflast_handoff_commit: none), not just commits made in this conversation turn; plus files changed, tests run, user decisions;Next:the user's stated intent (ask if unstated).- frontmatter →
last_handoff_commit: $(git -C <repo> rev-parse --short HEAD),branch,last_updated: today. ## 🕑 Session log→ prepend one dated line.- Milestone candidates → append
- [ ] confirm milestone "<name>" → /second-brain:analyze <repo>to## ✅ TODO. Do NOT touch milestone boxes.
- Update the Dashboard row for this repo only (Last session · Next · Updated). Row missing → add it.
- Sync L1:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/sync.sh" - Git hygiene: uncommitted/untracked changes in touched repos → flag them ("commit before you forget?"). Never commit for the user unless asked.
- Confirm in one line per repo: what was recorded + the anchor hash.
Rules
- Facts cited, intent labeled, unknown → ask. NEVER check milestone boxes (that is /second-brain:analyze's job). No transcript summaries.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

