wrap-up-session
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
git status --short
git diff --stat
git log --oneline -5
More from vishalsachdev/claude-code-skills
paper-writing
Expert guidance for writing high-quality academic and research papers. Use when the user wants to write, structure, revise, or improve academic papers, research articles, conference papers, or technical reports. Provides comprehensive support for all stages from planning to final polish.
744formbuilder-admin
>
5tweet-series-extractor
|
1start-session
Use when user says "let's get started", "where are we", or at beginning of a session. Reads project context from CLAUDE.md, checks git status and recent commits, and provides orientation for the session. Works across all repo types (code, research, mixed).
1codebase-singularity
Apply the codebase singularity approach: reliable codebase understanding and change with a repeatable workflow, guardrails, and verification gates. Use for repo work (feature, bugfix, refactor, migration) when you need high trust, minimal diffs, and explicit validation and exit criteria.
1agentic-validators
Design and install validation hooks for coding agents (e.g., Claude Code) to make AI changes safer and more deterministic. Use when you want post-tool-use or stop hooks, automated tests/linters/formatters, parallel subagents with per-file validation, or a repeatable “agent pipeline” with audit logs.
1