session-end

Save session context, reminders, and diary entries to GitHub.

64|19|Updated Mar 25, 2026

Search Tags:#session management #git integration #session wrap-up #progress saving #diary entry

Ready to run

npx skills add https://github.com/faizkhairi/claude-code-blueprint --skill session-end-faizkhairi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-end
Source: https://github.com/faizkhairi/claude-code-blueprint/tree/main/skills/session-end
Command: npx skills add https://github.com/faizkhairi/claude-code-blueprint --skill session-end-faizkhairi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the session wrap-up process, saving the current state and progress for future reference.

Core Features & Use Cases

Session Summary: Automatically saves a summary of the session's accomplishments.
Reminders Update: Updates reminders and moves completed ones to the Completed section.
Project Context: Updates the context for each project being worked on.
Memory Updates: Checks for new preferences, technical learnings, and decisions.
Diary Entry: Saves a diary entry if the session was significant.
Git Commit and Push: Commits changes to the memory files and pushes them to GitHub.

Quick Start

Use the session-end skill to save your current session and wrap up.

Frequently Asked Questions about session-end

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

FAQPage Schema

How do I automate session wrap-up and save coding progress for future reference?▼

Automating session wrap-up involves saving session context, updating reminders, storing project context, and committing memory files to GitHub. This captures accomplishments and technical learnings for future reference.

Can I commit local memory files and push progress updates directly to a GitHub repository?▼

Yes, committing local memory files and pushing progress updates to a GitHub repository is supported. The process commits changes to memory files, including session summaries and updated reminders, directly to the configured repository.

Does session wrap-up require a local memory file setup before saving project context?▼

Yes, session wrap-up requires access to local memory files to save project context and a GitHub repository for committing changes. These environments must be accessible to automatically extract and store session accomplishments.

What is the best way to save a diary entry and update reminders when ending a coding session?▼

Saving a diary entry and updating reminders during a coding session wrap-up is handled automatically if the session was significant. Completed reminders are moved to a Completed section while project context and technical decisions are recorded.

How does session management handle technical learnings and new preferences discovered during development?▼

Session management handles technical learnings by checking for new preferences and decisions during the wrap-up. These memory updates are saved alongside the session summary and then committed to the GitHub repository.

What happens to project context when automating the end of a coding session?▼

When automating the end of a coding session, project context is updated to reflect the current state of each project. This updated context, along with session summaries and diary entries, is saved and pushed to GitHub.