s-end-session

Save conversation memories, update GitHub issues, and generate session summaries.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gyarra/cine_medallo_2 --skill s-end-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: s-end-session
Source: https://github.com/gyarra/cine_medallo_2/tree/main/.claude/skills/s-end-session
Command: npx skills add https://github.com/gyarra/cine_medallo_2 --skill s-end-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ending sessions cleanly is hard without preserving context. This skill saves memories, updates issues, and generates a concise progress summary to maintain continuity across conversations and projects.

Core Features & Use Cases

  • Automatic memory capture: saves user preferences, decisions, and relevant references to the shared in-repo memory location (.claude/memory/).
  • Issue and task updates: creates or updates GitHub issues or trackers with a clear, actionable summary of progress.
  • Session wrap-up: produces a human-friendly progress report suitable for teammates, documentation, and handoffs.

Quick Start

Run the End Session skill at the end of a session to save memories, update issues, and generate a concise progress summary.

Frequently Asked Questions about s-end-session

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

FAQPage Schema
How do I save conversation context and generate a session summary at the end of a project workflow?

To generate a session summary and save context, run an end-session skill that automatically captures conversation memories, updates issue trackers, and produces a human-friendly progress report for handoffs and continuity.

What is in-repo memory management for persistent context across development sessions?

In-repo memory management stores persistent context under the .claude/memory directory, indexing decisions and preferences structurally so future conversations can retrieve branch-based memory versions for continuous project context.

How do I automatically update GitHub issues with progress summaries when ending a session?

You can automatically update GitHub issues with progress summaries by running an end-session workflow that creates or updates trackers with a clear, actionable summary of your session's progress and decisions.

Can I use branch-based memory versions to maintain separate session contexts for different project features?

Yes, branch-based memory versions allow you to maintain separate session contexts. The skill saves in-repo memory under .claude/memory with structured indexing, enabling future retrieval of context specific to each branch.

What's the best way to wrap up collaborative work sessions with persistent memory and documentation?

The best way to wrap up collaborative sessions is running an automated end-session process that captures memories, updates issues, and generates a concise progress report suitable for teammates, documentation, and project handoffs.

Do I need any external dependencies or components to save session memories and update issue trackers?

No external dependencies or components are required to save session memories and update issue trackers. The skill operates independently to store in-repo memory and generate structured session summaries.