rohitg00/pro-workflow

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.

First seen Feb 23, 2026

Installation

$ npx skills add rohitg00/pro-workflow --skill wrap-up

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from rohitg00/pro-workflow · top by installs.

npx skills add rohitg00/pro-workflow

Browse all from rohitg00/pro-workflow

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2.8K
Default branch main
Open issues 12
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,585 B
  • docs SUMMARY.md 222 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 131 installs

SKILL.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

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