Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
shipshitdev avatar

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-end

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs48
repo stars31
Last updatedAugust 2, 2026
Repositoryshipshitdev/library

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

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 to session-documenter

External Side Effects:

  • None

Confirmation Required:

  • Before rewriting existing session entries
  • Before promoting captured rules or skills outside session docs

Delegates To:

  • session-documenter
  • rules-capture for unresolved reusable preferences
  • skill-capture for 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-start reads 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 /clear manually 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

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.