mcpbeat

Wrap Up

rohitg00/wrap-up

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.

396 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
2755
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/rohitg00/pro-workflow --skill wrap-up

The instruction itself

7 sections, as written by the author

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

  • Changes Audit — What files were modified? Anything uncommitted? TODOs left in code?
  • Quality Check — Run lint, typecheck, and tests. All passing? Any warnings?
  • Learning Capture — What mistakes were made? What patterns worked well? Format as [LEARN] Category: Rule
  • Next Session Context — What's the next logical task? Any blockers? Context to preserve?
  • Summary — One paragraph: what was accomplished, current state, what's next.

Commands

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?"

How to use it

Copy the folder

Take rohitg00/wrap-up from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.