Agent skill · operations · vishalsachdev
wrap-up-session
Use when user says "let's wrap up", "close shop", "done for today", or wants to end a session. Handles session wrap-up including git operations, documentation updates, roadmap updates, and preparing for next session. Works across all repo types.
Why this skill is useful
Adds specific git commands and session management workflows that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-01. 4 stars on the source repository.
What this skill does
Close Shop Wrap up a work session. Execute these steps directly (do NOT spawn a subagent — you have the session context, a subagent does not). Steps 0. Read project wrap-up instructions Check CLAUDE.md for ## Session Wrap-up, ## Deployment, or similar sections. If the project has specific wrap-up steps (sync commands, restart commands, deploy scripts), note them — you'll run them in Step 4. 1. Review uncommitted work If there are uncommitted changes, ask the user what to do: Commit: Stage and commit with a descriptive message following the repo's existing commit style. Stash: git stash push -m "WIP: [description]" — for work-in-progress not ready to commit. /start-session will surface this next time. Leave: Note the uncommitted files in the session summary as carry-forward. 2. Push and update CLAUDE.md Push: After committing, push to the remote branch. Ask the user if unsure which branch. Update roadmap sections — skip if CLAUDE.md lacks these sections: ## Session Log — Keep only the 1 most recent entry in CLAUDE.md. Replace (don't append) the existing session log content with today's entry: Move any older entries to docs/session-archive.md. Create the archive file if it doesn't exist. claude-mem already stores full session history — the session log exists only so /start-session can show "last time + next steps." ## Roadmap — Check off completed items (- [ ] → - [x]). Infer completions from commits made during the session. ## Current Focus — Update to the next incomplete roadmap item, or ask the user. Commit and push the CLAUDE.md update. 2b. Memory dedup check Before writing anything to auto memory (~/.claude/projects//memory/), check: 1. Is this already in CLAUDE.md? If the fact is in the project's CLAUDE.md (architecture, env vars, commands, gotchas), don't duplicate it in auto memory. 2. Is this a session event? claude-mem records session observations automatically. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vishalsachdev/wrap-up-session