wrap-up
The wrap-up skill systematically concludes coding sessions by auditing modified files, running quality checks like linting and tests, documenting lessons learned, and generating a session summary with context for resuming work. Use it when ending a coding session or upon hearing phrases like "wrap up," "done for the day," or "finish coding" to ensure no uncommitted changes are overlooked and quality standards are maintained before closing the editor.
git clone --depth 1 https://github.com/rohitg00/pro-workflow /tmp/wrap-up && cp -r /tmp/wrap-up/skills/wrap-up ~/.claude/skills/wrap-upSKILL.md
# Wrap-Up Ritual End your coding session with intention. ## Trigger Use when ending a session, saying "wrap up", "done for now", or before closing the editor. ## Workflow 1. **Changes Audit** — What files were modified? Anything uncommitted? TODOs left in code? 2. **Quality Check** — Run lint, typecheck, and tests. All passing? Any warnings? 3. **Learning Capture** — What mistakes were made? What patterns worked well? Format as `[LEARN] Category: Rule` 4. **Next Session Context** — What's the next logical task? Any blockers? Context to preserve? 5. **Summary** — One paragraph: what was accomplished, current state, what's next. ## Commands ```bash git status git diff --stat npm run lint 2>&1 | head -20 npm run typecheck 2>&1 | head -20 npm test -- --changed --passWithNoTests ``` ## Learning Categories Navigation, Editing, Testing, Git, Quality, Context, Architecture, Performance ## Guardrails - Do not skip any checklist step. - If tests are failing, flag before ending session. - If uncommitted changes exist, ask whether to commit or stash. ## Output - Modified file list with uncommitted changes highlighted - Quality gate results - Captured learnings (if any) - One-paragraph session summary - Next session resume context After completing checklist, ask: "Ready to end session?"
Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.
Auto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.
Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".
Smart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual compact or when auto-compact triggers.
Analyzes and optimizes context window usage across sessions. Use when context feels bloated, sessions run slow, or approaching compaction limits.
Master the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to keep AI sessions sharp and efficient.
Optimize token usage and context management. Use when sessions feel slow, context is degraded, or you're running out of budget.