end-session
Skill16 starsChanged 7 months agoMITView on GitHub
Save session progress, extract lessons, update memory, push to GitHub if configured. Triggers on \"End Session\".
11 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 versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- 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
- markbaindesign/bain-studio★ 0same name
1 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 repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- actSkill
- security-checkSkill
- environment-checkSkill
- run-verificationSkill
- refactorSkill
- debug-session-archivedSkill
- generate-guardsSkill
- check-anthropicSkill
- code-reviewerSkill
- code-reviewSkill
- debug-sessionSkill
- evolve-checkSkill
- evolveSkill
- fix-bugSkill
- forgetSkill
- frontend-designSkill
- guardSkill
- kit-healthSkill
- learnSkill
- map-codebaseSkill
- modeSkill
- parallel-prototypesSkill
- planSkill
- powershell-safeSkill
- product-riskSkill
- progress-reportSkill
- prototype-hypothesisSkill
- recallSkill
- refactoring-uiSkill
- scan-codebaseSkill
- scan-conventionsSkill
- search-firstSkill
- search-memorySkill
- shadow-codeSkill
- skill-creatorSkill
- smart-resumeSkill
- start-sessionSkill
- strategic-compactSkill
- tourSkill
- ux-heuristicsSkill
- verification-loopSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Allowed Tools: Read, Edit, Write, Glob, Grep, Bash
- Very specific: line 20
Check which memory layout exists: .claude/memory/lessons.md or tasks/lessons.md
- Distinctive: line 24
If any runtime errors were solved this session, add them: Symptom | Root Cause | Fix
- Distinctive: line 28
If any approach was tried and discarded this session, log it with why it was rejected
- Distinctive: line 38
Add one-line summary of what changed
- Very specific: line 48
If output files exist, update plan status to SHIPPED
- Distinctive: line 51
If any planned task was completed this session, log estimated vs actual sessions
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: end-session
Trigger: "End Session"
Description: Save session progress, extract lessons, update memory, push to GitHub if configured.
Allowed Tools: Read, Edit, Write, Glob, Grep, Bash
Steps
- Extract lessons (
/learn):- Review conversation for bugs fixed, patterns discovered, decisions made
- Check which memory layout exists:
.claude/memory/lessons.mdortasks/lessons.md - Append lessons and decisions to whichever files exist
- Update error-lookup (
tasks/error-lookup.md):- If any runtime errors were solved this session, add them: Symptom | Root Cause | Fix
- Skip if no errors were encountered
- Update regret log (
tasks/regret.md):- If any approach was tried and discarded this session, log it with why it was rejected
- Skip if nothing was rejected
- Evolve check (
/evolve-checkif available):- Scan
tasks/skill_scores.mdfor skills that needed corrections - Report which skills are healthy vs need attention
- Skip if skill_scores.md is empty
- Scan
- Update STATUS.md (project root):
- Increment session number
- Add one-line summary of what changed
- Update MEMORY.md (
.claude/memory/MEMORY.md):- Set
currentDateto today's date and session number
- Set
- Update skill_usage.md (
tasks/skill_usage.md):- Log which skills fired this session with today's date
- Plan drift check:
- Glob
plans/for files marked "Ready to Code" or "In Progress" - If output files exist, update plan status to
SHIPPED
- Glob
- Update velocity (
tasks/velocity.md):- If any planned task was completed this session, log estimated vs actual sessions
- Skip if no planned tasks were completed
- Push memory (if memory.ps1 exists in project root):
Skip silently if memory.ps1 doesn't exist.powershell -NoProfile -ExecutionPolicy Bypass -File memory.ps1 push - Report:
Session complete. **Session N** -- [one-line summary] **Lessons extracted:** N - [one line per lesson] **Errors logged:** N (or "none") **Regrets logged:** N (or "none") **Files touched:** [list]
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.

