Se4thvin Plugins
- 2 repo stars
- Updated May 13, 2026
- se4thvin/context-handoff
se4thvin-plugins is a Claude Code marketplace plugin that saves structured session handoff Markdown before context runs out and resumes prior work cleanly in the next session with `/handoff` and `/handoff-resume`.
About
context-handoff is a Claude Code plugin for checkpointing agent session state before context exhaustion. `/handoff` writes a structured Markdown file to `./.handoffs/` (override with `HANDOFF_DIR`) capturing current task, completed work, in-progress changes, next steps, blockers, and key file paths. `/handoff-resume` lists recent handoffs and reloads the chosen checkpoint. Sections include git branch, working directory, timestamp, and optional slug filenames like `/handoff before-refactor`. The `writing-handoff` skill triggers on explicit commands, save-state phrases, or context-exhaustion signals—but not generic wrap-up phrases. Install with `/plugin marketplace add se4thvin/context-handoff` and `/plugin install context-handoff`.
- /handoff writes structured Markdown with 6 sections: task, completed, in-progress, next steps, blockers, key context
- /handoff-resume picker loads numbered checkpoints newest-first
- Default output directory ./.handoffs/ overridable via HANDOFF_DIR env var
- Captures git branch, working directory, and timestamp in handoff header
- Conservative auto-trigger on context-exhaustion phrases only
Se4thvin Plugins by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add se4thvin/context-handoffAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Last updated | May 13, 2026 |
| Repository | se4thvin/context-handoff ↗ |
How do you resume Claude Code after context limits?
Run `/handoff before-refactor` to write a Markdown checkpoint with commits, blockers, and next steps before starting a new Claude session.
Who is it for?
Developers running long Claude Code sessions who need reliable checkpoints before context compaction or multi-day task continuity.
Skip if: Teams wanting automatic git-based work tracking without manual `/handoff` invocation or shared team knowledge bases beyond local Markdown files.
What you get
Timestamped Markdown handoff files in `.handoffs/` with task status, file paths, commits, blockers, and prioritized next steps for session resume.
- Structured handoff Markdown files
- Session resume summaries
By the numbers
- Handoff files capture 6 structured sections plus git branch header
- Default handoff directory is ./.handoffs/ (configurable via HANDOFF_DIR)
Recommended Marketplaces
How it compares
Use context-handoff for lightweight local Markdown session checkpoints rather than external PM tools or vector memory databases.
FAQ
What does a context-handoff file contain?
context-handoff files include six sections: current task, completed work, in-progress changes, next steps, blockers/open questions, and key context with file paths and conventions. The header records project name, working directory, git branch, and timestamp.
When does context-handoff trigger automatically?
context-handoff auto-triggers on explicit `/handoff`, phrases like save state or running low on context, and auto-compaction reminders. It does not trigger on generic session-ending phrases like wrap up or stop for today.