
Session End
- 48 installs
- 31 repo stars
- Updated August 2, 2026
- shipshitdev/library
Helps with ai & agent building tasks.
About
session-end is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.
- session-end
- AI & Agent Building
- AI-coding skill
Session End by the numbers
- 48 all-time installs (skills.sh)
- +3 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #7,411 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/shipshitdev/library --skill session-endAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 48 |
|---|---|
| repo stars | ★ 31 |
| Last updated | August 2, 2026 |
| Repository | shipshitdev/library ↗ |
What it does
Helps with ai & agent building tasks.
Files
Session End
Document your session before clearing context. This is a TWO-STEP process: /session-end documents, then user manually runs /clear.
Contract
Inputs:
- Redacted session context and changed-file summary
- Pending tasks, blockers, decisions, and reusable rules/workflows
Outputs:
- Saved session documentation with secrets removed
- Clear next-step instruction for context reset
Creates/Modifies:
.agents/sessions/YYYY-MM-DD.md- Related
.agents/task or summary files when delegated tosession-documenter
External Side Effects:
- None
Confirmation Required:
- Before rewriting existing session entries
- Before promoting captured rules or skills outside session docs
Delegates To:
session-documenterrules-capturefor unresolved reusable preferencesskill-capturefor reusable workflows that should become skills
Workflow
Step 1: Document Session
When invoked, immediately:
1. Run the session-documenter skill to save a redacted session summary 2. Let it complete — it will document tasks, decisions, files changed, patterns, and mistakes without storing secrets 3. Confirm documentation saved
Cross-platform note: If your agent platform doesn't support skill invocation, follow the session-documenter workflow manually by reading the session-documenter skill definition.Step 2: Remind User to Clear
After documentation is complete, tell the user:
Session documented to .agents/sessions/YYYY-MM-DD.md
NEXT STEP: Run /clear to clear the conversation context.
Your session is safely preserved and will be loaded on next /session-start.Why This Matters
- WITHOUT documentation: all context is lost forever, next session has no idea what was done
- WITH documentation: context preserved, next
/session-startreads the session file, continuity maintained
Important Notes
- ONE FILE PER DAY: Session documenter appends to the same day's file
- Multiple invocations: Each one adds a new session entry
- Does NOT clear context: User must run
/clearmanually after - Redaction is mandatory: Do not store API keys, tokens, passwords, cookies,
private credentials, or secret values from the conversation. Replace them with [REDACTED_SECRET] and summarize the surrounding context.
Related Skills
- session-start — Loads preferences and today's session after clearing
- session-documenter — The underlying documentation skill
{
"name": "session-end",
"version": "1.0.0",
"description": "Document session context before clearing conversation",
"author": {
"name": "Ship Shit Dev",
"email": "hello@shipshit.dev",
"url": "https://shipshit.dev"
},
"license": "MIT",
"skills": "."
}