vibe-handoff — Claude Code skill: what it does, how to install
Creates a compact project handoff for another session or coding tool. It captures current work without copying chat transcripts or secrets.
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-handoff -a claude-codeWhat vibe-handoff does
The skill inspects the current branch and revision, working-tree changes, MEMORY.md, the project manifest, recorded decisions, and available check results. It then writes a short handoff covering the objective, current state, changed files, decision rationale, blockers, checks with their dates and results, unchecked items, a recovery checkpoint, and one bounded next action.
Product documents are referenced instead of copied into the handoff. The workflow leaves out secrets, credentials, unnecessary personal data, and full transcripts. Stable project rules belong in AGENTS.md; stale progress in MEMORY.md is replaced rather than expanded into an endless log.
The skill does not mark a check as successful without an actual result, and it does not commit uncommitted changes. It needs access to the project files and the repository’s current state.
What it helps with
- prepare project context for a new session
- record changed files and the reasoning behind decisions
- separate completed checks from checks that were not run
- set a recovery point and a bounded next action
- hand work to another tool without exposing secrets
Example prompts for the agent
- Prepare a handoff for the current task and save it to
MEMORY.md. - Inspect the branch, working-tree changes, and check results, then list blockers and the next bounded action.
- Refresh the project context and reference product documents instead of copying their contents.
How to install vibe-handoff
1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-handoff -a claude-code2Manually: put the files in place
~/.claude/skills/vibe-handoff/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vibe-handoff/
1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-handoff -a codex2Manually: put the files in place
.agents/skills/vibe-handoff/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-handoff -a cursor2Manually: put the files in place
.cursor/skills/vibe-handoff/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install KhazP/vibe-coding-prompt-template vibe-handoff2Manually: put the files in place
.github/skills/vibe-handoff/SKILL.md1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-handoff -a gemini-cli2Platform CLI
gemini skills install https://github.com/KhazP/vibe-coding-prompt-template --path workflow/skills/vibe-handoffManually: put the files in place
.devin/skills/vibe-handoff/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-handoff -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vibe-handoff
How do I install vibe-handoff in Claude Code?
Run npx skills add KhazP/vibe-coding-prompt-template --skill vibe-handoff -a claude-code, then check ~/.claude/skills/vibe-handoff/SKILL.md.
What does vibe-handoff do?
It turns the project’s current state into a handoff for another session or coding tool. The handoff records decisions, changes, checks, blockers, a recovery point, and the next bounded action.
Which platforms does vibe-handoff support?
The skill is available for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.
Source text
SKILL.md · MIT
--- name: vibe-handoff description: Prepare compact factual project context for another session or coding tool without copying transcripts or secrets. allowed-tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion --- # Vibe Handoff Inspect the current branch/revision, working-tree changes, MEMORY.md, manifest, decisions, and available check results. Write a compact handoff with objective, current state, changed files, decisions and rationale, blockers, actual checks with date/results, unperformed checks, recovery checkpoint, and the next bounded action. Reference product documents instead of duplicating them. Exclude secrets, credentials, personal data unnecessary for continuation, and full transcripts. Do not infer successful checks or commit uncommitted changes. Keep stable rules in AGENTS.md and replace stale progress in MEMORY.md rather than appending an unlimited log.
© KhazP · MIT · KhazP/vibe-coding-prompt-template
