end-session

Log work sessions and push Markdown summaries to the ai-history repository.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/shankur/dots --skill end-session-shankur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: end-session
Source: https://github.com/shankur/dots/tree/main/dot_claude/skills/end-session
Command: npx skills add https://github.com/shankur/dots --skill end-session-shankur

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users efficiently log and summarize their work sessions, ensuring that key findings, decisions, and follow-ups are captured for future reference.

Core Features & Use Cases

  • Session Summary: Automatically generates a summary of the session, including what was done, the approach taken, key findings, and follow-ups.
  • Project Identification: Determines the project name based on the current working directory.
  • UUID Generation: Generates a unique identifier for the session.
  • Date and Path Construction: Constructs the output path for the session summary file.
  • File Writing: Writes the session summary file in Markdown format.
  • Git Operations: Performs Git commands to stage, commit, and push the file to the ai-history repository.

Quick Start

End your current session and create a summary by running the command: end-session.

Frequently Asked Questions about end-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically log and summarize work sessions in Markdown?

You can automatically log work sessions by running a command that identifies the project from the current directory, generates a unique identifier, and writes a Markdown summary file to the ai-history repository.

What is included in an automated session summary?

An automated session summary includes what was done, the approach taken, key findings, and follow-ups, ensuring that critical project decisions are captured for future reference in Markdown format.

Do I need Git configured to push session logs to the ai-history repository?

Yes, you need Git configured because the Skill performs Git operations to stage, commit, and push the generated Markdown session summary file directly to the ai-history repository.

How does project identification work when generating a work summary?

Project identification works by automatically determining the project name based on the current working directory, which is then used to construct the output path for the Markdown session summary file.

Can I use this session logging tool without a unique identifier for each session?

No, the session logging process automatically generates a unique identifier for each session to construct the output path and distinctly track the Markdown summary file within the ai-history repository.

What are the limitations of automatically committing work summaries to Git?

A limitation is that the Git operations automatically stage, commit, and push the Markdown file specifically to the ai-history repository, meaning session logging depends on this exact repository structure being available.