Stats
Actions
Tags
From workflow-tools
Protocol for cleanly ending a work session including filing issues, running quality gates, updating status, committing, and handing off context. Use when wrapping up a coding session.
How this skill is triggered — by the user, by Claude, or both
Slash command
/workflow-tools:session-completionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**When ending a work session**, complete these steps to ensure clean handoff and no lost context.
When ending a work session, complete these steps to ensure clean handoff and no lost context.
Create issues for anything that needs follow-up:
Run the project's quality checks:
mix test, zig build test, npm test, etc.)git add <specific files>
git commit -m "message"
If using an issue tracker that stores files in the repo (e.g., Beads), sync those changes too.
Provide context for the next session:
git push automatically - the user will push manuallygit commit automatically - only commit when the user explicitly asksSession ending. Here's the status:
1. Completed:
- [What was finished]
2. In Progress:
- [What's partially done, with context]
3. Issues Filed:
- [New issues created for follow-up]
4. Next Steps:
- [What to focus on next session]
Clean session completion ensures:
npx claudepluginhub code0100fun/botfiles --plugin workflow-toolsWraps up a work session by recording changed files, caveats, decisions, and next steps so a fresh session can resume without re-deriving context.
Audits code changes, runs quality checks, captures learnings, and generates a session summary when ending a coding session.
Wraps up sessions by verifying tests/build/lint with pnpm, committing via /commit, updating .claude/project-diary.md and build-status.md, generating handoff messages.