plugins-claude/session/skills/session-handoff/SKILL.md
Push work and record handoff context for cross-machine pickup
npx skillsauth add st0nefish/claude-toolkit session-handoffInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Commit all work, push, and record handoff context on the linked issue for cross-machine pickup.
Gather current state:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/catchup
Based on catchup output and conversation context, construct the handoff content:
WIP commit body (what changed — lives in git history):
=== IN PROGRESS ===
- <current state of work, partial implementations, files touched>
Issue comment (what to do next — lives on the issue, accessible without cloning):
=== HANDOFF ===
Branch: <branch>
Timestamp: <ISO 8601>
From: <hostname>
=== NEXT STEPS ===
- <ordered list of what to tackle on the other machine>
=== KEY CONTEXT ===
- <decisions made, gotchas, environment details, important state>
Create the WIP commit:
BRANCH=$(git rev-parse --abbrev-ref HEAD)
TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
HOSTNAME=$(hostname -s 2>/dev/null || echo "unknown")
git add -A
git commit --no-verify -m "WIP: <first line of IN PROGRESS>
=== HANDOFF === Branch: $BRANCH Timestamp: $TIMESTAMP From: $HOSTNAME
=== IN PROGRESS === <in-progress content>
=== FILES IN THIS COMMIT === $(git diff --cached --name-only)" git push
Substitute all template values with actual content before executing. If `git push` fails, the commit still exists locally — inform the user to push manually.
4. If the current branch matches `type/NNN-*`, post the handoff comment to the linked issue:
cat > /tmp/handoff-comment.md << 'EOF'
<issue comment content from step 2>
EOF
bash ${CLAUDE_PLUGIN_ROOT}/scripts/git-cli issue comment <N> --body-file /tmp/handoff-comment.md
rm -f /tmp/handoff-comment.md
git pull && /session:session-resume on the other machine/session:session-resume on the other machinedevelopment
Start work from your description — explore the codebase and plan
data-ai
Multi-phase, multi-agent feature workflow: spec → plan → refine → divide → execute → review. Invoke when the user escalates a session-start/session-issue flow to orchestration, or asks to run a non-trivial feature (multiple files, design ambiguity, cross-cutting concerns, correctness-critical paths) through the full multi-agent workflow. For small fixes, prefer session-start.
tools
Browse open issues, pick one, and start work on it
tools
Interact with GitHub and Gitea issue trackers and CI systems. List and show issues, file bugs, comment on issues or PRs, list and show pull requests, and fetch CI run logs — all from any repo context without leaving the session.