Session Wrap-Up
@branexp
npx machina-cli add skill @branexp/session-wrap-up --openclawSession 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
cd <workspace>
git add -A
git status
git commit -m "wrap-up: YYYY-MM-DD session summary"
git push
Notes:
- The wrap-up
git pushis automatic (no confirmation prompt). - If
git pushfails, 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
Session Wrap-Up seals the current conversation before starting a new one. It captures key topics, decisions, and solutions, flushes context to memory files, updates PARA notes, and commits a summary so transitions between sessions stay seamless.
How This Skill Works
Triggered by a user cue such as wrap up or /session_wrap_up, it writes to memory/YYYY-MM-DD.md with topics discussed, decisions, commands or code that worked, problems solved, and lessons learned. If significant learnings occurred, it updates MEMORY.md and refreshes PARA notes under notes/areas, notes/projects, and notes/resources. Finally, it commits the changes with a date-stamped message and presents a concise summary to the user, including what was captured and what to follow up on.
When to Use It
- After a long support or brainstorming session to preserve context
- Before starting a new task or session to ensure a clean slate
- When the user explicitly asks to wrap up the current session
- At the end of the workday to archive progress and lessons learned
- When a project milestone completes and transition notes are needed
Quick Start
- Step 1: Trigger the wrap-up by saying a cue (wrap up /session_wrap_up).
- Step 2: The system writes memory/YYYY-MM-DD.md, updates MEMORY.md if needed, refreshes PARA notes, and commits changes with a date-stamped message.
- Step 3: The system presents a concise summary and signals readiness for a new session ⚡
Best Practices
- Ensure the daily log file memory/YYYY-MM-DD.md exists or is created
- Capture key topics, decisions, working commands, problems solved, and lessons learned
- Update MEMORY.md only if significant learnings occurred
- Refresh PARA notes (areas, projects, resources) and mark open loops as completed when applicable
- Use a date-stamped commit message and allow the automatic push to run
Example Use Cases
- A support chat ends; wrap-up runs, creating memory/2026-03-08.md with topics and decisions, then MEMORY.md is updated and PARA open-loops are adjusted.
- Design sprint concludes; wrap-up updates notes/projects with progress, commits wrap-up: 2026-03-08 session summary, and pushes automatically.
- Bug triage session wraps up; summary lists commands that worked and problems solved, with memory and PARA updates.
- AI training session ends; wrap-up records lessons learned and updates resources in PARA for reference in future sessions.
- End-of-day wrap-up archives the day's work, prepares transition notes for the next session, and confirms the commit and push.
