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?"
Analyzes and optimizes context window usage across sessions. Use when context feels bloated, sessions run slow, or approaching compaction limits.
Analyze session token usage and cost patterns. Identify expensive operations and recommend optimizations. Use to understand and reduce session costs.
Specialized debugging agent. Use when facing hard bugs, test failures, or runtime errors that need systematic investigation.
Multi-phase development agent. Research > Plan > Implement with validation gates. Use PROACTIVELY when building features that touch >5 files or require architecture decisions.
Analyze permission denial patterns and generate optimized alwaysAllow/alwaysDeny rules. Use when permission prompts slow down workflow.
Break down complex tasks into implementation plans before writing code. Use when task touches >5 files, requires architecture decisions, or has unclear requirements.
Code review specialist that verifies every finding against actual code before reporting. Use before committing, for PR reviews, or after major changes.
Confidence-gated exploration that assesses readiness before implementation. Scores 0-100 across five dimensions and gives GO/HOLD verdict.