session-close

Summarize research work, update memory logs, commit changes, and push to version control.

39|4|Updated Feb 3, 2026

Search Tags:#workflow #research #version control #commit #organize #session summary #memory log

Ready to run

npx skills add https://github.com/swarm-ai-research/swarm --skill session-close-swarm-ai-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-close
Source: https://github.com/swarm-ai-research/swarm/tree/main/.skills/session-close
Command: npx skills add https://github.com/swarm-ai-research/swarm --skill session-close-swarm-ai-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The problem addressed by this Skill is the challenge of maintaining a consistent and organized research workflow that ensures no work is lost and that future sessions can be seamlessly continued from where they left off.

Core Features & Use Cases

End-of-Session Ritual: Summarizes changes, updates memory, and commits code.
Inventory Changes: Lists modified, added, and deleted files.
Session Summary: Encourages reflection on what was learned and what comes next.
Memory Update: Appends session information to the memory logs.
Commit and Push: Ensures that all changes are safely stored in a repository.

Quick Start

To close your research session, run the session-close skill. It will guide you through the process of summarizing your work and ensuring everything is safely saved and pushed.

Frequently Asked Questions about session-close

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

FAQPage Schema

How do I summarize research work and commit changes at the end of a session?▼

An end-of-session ritual summarizes research work by inventorying modified files, appending reflections to memory logs, and pushing commits to version control. This structured workflow ensures no work is lost and future sessions resume seamlessly.

What is the best way to maintain a research workflow without losing context?▼

Maintaining a research workflow without losing context requires appending session summaries to memory logs before committing changes. By documenting what was learned and what comes next, researchers preserve context and ensure organized version control across sessions.

How do I inventory modified files and update memory logs before committing research?▼

Automated session close inventories modified, added, and deleted files, then appends session information to memory logs to preserve context. This process ensures all changes are documented and safely committed to version control.

Can I use an automated session summary for individual research workflows?▼

Automated session summaries support both individual researchers and research teams. The workflow guides you through reflecting on changes, updating memory logs, and committing work to version control regardless of team size.

When do I need a structured ritual to close out research sessions?▼

A structured close ritual is needed for continuous research spanning multiple sessions. It ensures your session summary and memory updates are consistently committed to version control, preventing lost work and context drift.

Does closing a research session require a version control system to push changes?▼

Pushing changes to a version control system is a core part of closing a research session. It ensures all modified files, memory log updates, and session summaries are safely stored and accessible for future workflow continuity.