wrap-up · rohitg00 — Claude Code skill: session review and setup
The wrap-up skill audits code changes, runs quality checks, and records what to pick up next. Use it when you are about to end a coding session.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat wrap-up does
Before you leave, the skill reviews changed files, uncommitted work, and TODOs left in code. It runs lint, type checking, and tests with npm run lint, npm run typecheck, and npm test -- --changed --passWithNoTests; command output is limited to its first lines.
It records takeaways in the [LEARN] Category: Rule format, writes a session summary, and saves context for the next task. The report includes the modified files and quality-check results. Failing tests are flagged, and uncommitted changes trigger a question about committing or stashing them. Resolve that choice before ending the session.
What it helps with
- review changed files and uncommitted work
- spot TODOs left in code
- run lint, type checking, and tests
- record lessons and the next task
Example prompts for the agent
- Wrap up this coding session: review the changes, run the checks, and leave context for next time.
- I’m done for today. Summarize what changed and what I should tackle next.
How to install wrap-up
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowThis installs the whole pro-workflow plugin with all its skills
2Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill wrap-up -a claude-code3Manually: put the files in place
~/.claude/skills/wrap-up/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/wrap-up/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill wrap-up -a codex2Manually: put the files in place
.agents/skills/wrap-up/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill wrap-up -a cursor2Manually: put the files in place
.cursor/skills/wrap-up/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rohitg00/pro-workflow skills/wrap-up2Manually: put the files in place
.github/skills/wrap-up/SKILL.md1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill wrap-up -a gemini-cli2Platform CLI
gemini skills install https://github.com/rohitg00/pro-workflow --path skills/wrap-upManually: put the files in place
.devin/skills/wrap-up/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about wrap-up
How do I install wrap-up in Claude Code?
Run /plugin marketplace add rohitg00/pro-workflow, then run /plugin install pro-workflow@pro-workflow.
What does wrap-up do?
It reviews edits and uncommitted work, runs lint, type checking, and tests, then prepares a session summary and continuation context.
What happens if tests fail?
The skill flags failing tests before the session ends. If it finds uncommitted changes, it asks whether to commit or stash them.
Source text
SKILL.md · MIT
--- name: wrap-up description: End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session. user-invocable: true --- # 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?"
© Rohit Ghumare · MIT · rohitg00/pro-workflow
Similar skills
SKILL.md skills catalog →wrap-up by other authors comes first.