Capture git and project state into HANDOFF.md and claude-progress.txt.
npx skills add https://github.com/Asher-Plihal/claude-skills --skill handoff-asher-plihal
Please help me install this Agent Skill. Skill: handoff Source: https://github.com/Asher-Plihal/claude-skills/tree/main/handoff Command: npx skills add https://github.com/Asher-Plihal/claude-skills --skill handoff-asher-plihal
It prevents lost context when switching to a fresh chat by capturing the current repo state, committing progress, and generating a single, ready-to-paste continuation prompt.
claude-progress.txt.HANDOFF.md that becomes the authoritative source for what to resume next, including feature status from feature_list.json and worktrees from WORKTREES.md or equivalent.Trigger the skill when Asher types /handoff (or phrases like “pass to new chat” or “prepare a handoff”) to commit progress, generate HANDOFF.md, and receive a copy-paste prompt for the new chat.
High-intent search queries and answers about installing and using this skill.
To preserve uncommitted git changes during a session handoff, the skill stages file-specific in-progress work, commits it safely, and updates a progress tracking file so the new chat receives full repository context without information loss.
The best way to create a context handoff document is to generate a structured HANDOFF.md that records git status, recent commits, and feature status from feature_list.json, serving as the authoritative source to resume workflow in a fresh chat.
You generate a continuation prompt by capturing the current branch, last commit, and the exact next step into a single paste-ready block, allowing a fresh chat to resume active development immediately without manual context rebuilding.
Yes, the handoff process works with existing progress tracking files by updating claude-progress.txt and feature_list.json during ordered phases that capture project state, ensuring session continuity across chat switches.
Yes, you can prepare a repository handoff without raw output by recording git status, commit history, and diffs internally, then writing the summarized context into HANDOFF.md and a clean continuation prompt for the new session.
You should use an automated session handoff when switching chats during active development with uncommitted changes, because it prevents lost context by committing progress and generating a structured handoff document rather than relying on manual explanations.
DeL-TaiseiOzakiCapture CLI logs and Git activity into centralized checkpoint files.
amaledtuningGenerate a ready-to-paste continuation prompt with session state and next steps.
kirvinFetch upstream changes and rebase the current Git branch onto them.
elithrarAnalyze session history and git state to generate structured commit-message summaries.