Prepend a timestamped Recap and Next Actions to .claude/journal.md.
npx skills add https://github.com/kok1eee/o-m-cc --skill handoff-kok1eee
Please help me install this Agent Skill. Skill: handoff Source: https://github.com/kok1eee/o-m-cc/tree/main/skills/handoff Command: npx skills add https://github.com/kok1eee/o-m-cc --skill handoff-kok1eee
Long interactive LLM sessions can exhaust context windows and are difficult to continue across machines; this Skill captures a concise Recap and concrete Next Actions so work can resume immediately on the same or a different host. It removes ambiguity about what was discovered and what to do next by recording a timestamped, versionable journal entry that can be shared via VCS.
Run the handoff skill to append a concise Recap and concrete Next Actions to .claude/journal.md so another session or machine can resume work.
High-intent search queries and answers about installing and using this skill.
To resume a long Claude session across machines, you need a session handoff mechanism that writes a concise Recap and Next Actions to a journal file. This allows a new session to read the journal and immediately continue the work with full context.
Writing a session journal to a markdown file helps cross-EC2 continuation by creating a versionable checkpoint. The journal records discoveries and next steps, which you can share via VCS to let another EC2 instance pull the history and resume work immediately.
The best way to create a session checkpoint for an interactive LLM workflow is to generate a timestamped journal entry containing a session recap and a concrete list of next actions. Prepending this entry to a markdown file preserves existing history for later review.
Yes, you can use a markdown journal file for cross-machine session handoff without losing existing history. The handoff process prepends new Recap and Next Actions entries to the top of the file, preserving all previous journal records without editing them.
If no next actions are specified when creating a session recap, the process prompts the user to provide them. In headless mode where prompting is not possible, a placeholder is recorded to ensure the journal entry structure remains complete.
Yes, the session handoff journal records an optional short hostname alongside the timestamp for cross-machine identification. If hostname retrieval fails, the process tolerates the error by omitting host info and still writing the recap.
damilola-elegbede-orgSyncs validated system-configs/.claude/ files to the local ~/.claude/ directory.
jrmatherlyBootstrap session context with Serena memories, claude-mem observations, and git state.
SilentFlowerAppend session summaries and commit hashes to repository journal files.
harperreedAnalyze Claude Code session logs with jq to generate improvement proposals.
