wrap-up-session_skill

Overview

This skill wraps up a work session cleanly across all repo types. It launches an autonomous wrap-up agent (use model "opus") to run checks, commit changes, update documentation and roadmap sections, and prepare actionable next steps. It also provides guidance for syncing changes to another machine.

How this skill works

Before launch the skill checks for uncommitted work and reads CLAUDE.md to determine repo type and any wrap-up instructions. It starts the wrap-up-session agent (model: "opus") which runs linting/tests for code repos, commits document changes for research repos, updates roadmap sections in CLAUDE.md, and creates TODOs for the next session. After the agent completes, it recommends a non-interactive sync step to copy changes to another machine so work can continue seamlessly.

When to use it

• User says "let's wrap up", "close shop", "done for today", or requests session end
• Finishing a focused coding or writing block and you want a tidy checkpoint
• You need commits, roadmap updates, and a clear next-task list before switching machines
• Before handing off work to another team member or device
• At the scheduled end of a pairing or solo work session

Best practices

• Check git status first and resolve any obvious conflicts before launching the agent
• Ensure CLAUDE.md exists and contains a type: declaration to guide behavior; default to code behavior if absent
• Use model: "opus" when launching the wrap-up agent to ensure correct runtime
• Review the agent’s proposed commit messages and roadmap changes before final push
• Run the recommended non-interactive sync (unison -batch -terse) to mirror changes on the other machine

Example use cases

• End-of-day wrap for a Python project: run linters, tests, commit fixes, update roadmap and TODOs
• Wrapping a research/writing session: commit drafts, update word counts and current-section notes in CLAUDE.md
• Mixed repo: run code checks for src changes and commit documentation edits, then update roadmap
• Handover: produce a clear Session Log entry and Next list so the next person can resume immediately
• Switching machines: wrap up locally and run the recommended sync to avoid lost work