home / skills / openclaw / skills / session-wrap-up

session-wrap-up skill

/skills/branexp/session-wrap-up

This skill wraps up a session by flushing context to memory, updating PARA notes, committing changes, and delivering a concise summary for continuity.

npx playbooks add skill openclaw/skills --skill session-wrap-up

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
2.6 KB
---
name: session-wrap-up
description: Wrap up a conversation session before starting a new one. Use when the user says "wrap up", "wrap up this conversation", "session wrap up", or uses /session_wrap_up command. Flushes context to memory files, updates PARA notes, commits changes, and provides a summary.
---

# Session Wrap Up

End-of-session protocol to preserve context and ensure continuity between sessions.

## When Triggered

Run this protocol when the user indicates they want to wrap up the current session before starting a new one.

## Protocol Steps

Execute these steps in order:

### 1. Flush to Daily Log

Write to `memory/YYYY-MM-DD.md` (create if doesn't exist):
- Key topics discussed in this session
- Decisions made
- Commands, configs, or code that worked
- Problems solved and how they were solved
- Any gotchas or lessons learned

### 2. Update Long-Term Memory

If significant learnings occurred, update `MEMORY.md`:
- New user preferences discovered
- Important lessons learned
- Long-term decisions made
- Workflow changes

### 3. Update PARA Notes

Check and update the PARA structure in `notes/` (or `memory/notes/`):
- **Open loops** (`notes/areas/open-loops.md`): Add new unfinished items, mark completed items with ✅
- **Projects** (`notes/projects/`): Update progress on active projects
- **Areas** (`notes/areas/`): Add new ongoing responsibilities
- **Resources** (`notes/resources/`): Add new reference material, how-tos

### 4. Commit Changes

```bash
cd <workspace>
git add -A
git status
git commit -m "wrap-up: YYYY-MM-DD session summary"
git push
```

Notes:
- The wrap-up `git push` is **automatic** (no confirmation prompt).
- If `git push` fails, report the error and leave the commit locally.

### 5. Report Summary

Provide a brief summary to the user:
- What was captured
- Files updated
- Any items that need follow-up next session
- Confirmation that changes were committed (and pushed, if successful)

## Example Output

```
## Session Wrap-Up Complete ✅

**Captured to daily log:**
- Configured PARA second brain
- Fixed vector indexing for notes
- Set up weekly memory review cron

**Updated:**
- MEMORY.md: Added memory system learnings
- notes/areas/open-loops.md: Marked .gitignore task complete

**Committed:** `wrap-up: 2026-01-30 session summary`

**Follow-up next session:**
- Check LanceDB autoCapture setting
- Consider morning briefing cron

Ready for new session! ⚡
```

## Notes

- Always create the daily log file if it doesn't exist
- Use the current date for filenames and commit messages
- Keep summaries concise but complete
- Include the ⚡ emoji at the end (GigaBot signature)

Overview

This skill performs an end-of-session wrap-up to preserve context and ensure continuity before starting a new conversation. It flushes session details into daily memory files, updates long-term memory and PARA notes, commits changes to the workspace, and returns a concise summary of what was captured.

How this skill works

When triggered, the skill writes key session topics, decisions, working commands, solved problems, and lessons into a dated daily log file. It then updates long-term MEMORY.md if significant learnings exist, adjusts PARA notes (open loops, projects, areas, resources), runs a git commit/push sequence, and reports what was changed and any follow-ups needed. If git push fails, the error is reported and the commit remains local.

When to use it

  • User says "wrap up" or "wrap up this conversation"
  • User issues the /session_wrap_up command
  • You are closing a session and want a persistent record
  • Before switching tasks or starting a new conversation

Best practices

  • Always create the daily log file for the current date if it doesn't exist
  • Keep daily log entries concise: topics, decisions, commands, fixes, lessons
  • Only write into MEMORY.md for meaningful, long-term learnings or preferences
  • Mark completed open-loops with ✅ and add new unfinished items to open-loops
  • Run the commit/push automatically but report push failures clearly

Example use cases

  • After a troubleshooting session: log the fix, commands used, and root cause
  • After configuring a new tool: add configuration steps to resources and memory
  • When a user states new preferences: add them to MEMORY.md for future use
  • At day-end: create a daily log and update project progress in notes/projects

FAQ

What files are always created or updated?

The daily log memory/YYYY-MM-DD.md is always created or updated; PARA notes and MEMORY.md are updated as needed.

What happens if git push fails?

The skill reports the push error to the user and leaves the commit locally for manual or later retry.

Will the skill ask before pushing commits?

No. The wrap-up git push is automatic. Any failures are reported immediately.