claude-transfer

Writes pointer-based session handoff briefs for resuming work in fresh Claude sessions.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/dxiiren/project-skeleton --skill claude-transfer-dxiiren
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-transfer
Source: https://github.com/dxiiren/project-skeleton/tree/main/.claude/skills/claude-transfer
Command: npx skills add https://github.com/dxiiren/project-skeleton --skill claude-transfer-dxiiren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you close a Claude Code session mid-task, all working context is lost, and dumping a full transcript into the next session causes context rot and poisons unrelated work. This Skill writes a lean, pointer-based handoff brief to a git-ignored folder that a fresh session reads only on explicit resume, keeping auto-loaded memory clean. ## Core Features & Use Cases - Close mode: Drafts a one-page handoff brief in plan mode with DONE/IN PROGRESS/NEXT buckets, evidence-tagged facts, file pointers (path:line), recent commit hashes, open questions, and dead-ends, saved to .claude/workspace/reports/transfers/claude/. - Resume mode: Reads the latest brief, re-opens every pointed-to file fresh, checks recent git log, and runs a basic functional check to catch drift before continuing work. - Poison-free storage: Briefs live in a git-ignored, opt-in-only location and never touch CLAUDE.md or .claude/memory/, so unrelated sessions stay uncontaminated. - Use Case: You are halfway through a refactor at end of day. Run /claude-transfer close refactor-auth, and tomorrow a fresh session runs /claude-transfer resume to pick up exactly where you left off. ## Quick Start Ask Claude to close this session and write a handoff brief so you can resume the current task in a new session later.

Frequently Asked Questions about claude-transfer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off a Claude Code session to continue later?▼

Run `/claude-transfer close` to write a lean handoff brief with the current state, file pointers, and next steps to a git-ignored folder. Later, run `/claude-transfer resume` in a fresh session to read the brief, re-verify the repo state, and continue.

What is the difference between claude-transfer and llm-transfer?▼

claude-transfer targets a fresh Claude session on the same repository, so it uses pointers to files instead of pasted content. llm-transfer targets external LLMs without repo access, so it embeds full payloads for copy-paste.

Does the handoff brief get committed to git?▼

No. Briefs are written to `.claude/workspace/reports/transfers/claude/`, which is covered by the existing git-ignored `.claude/workspace/` rule. They stay local and are never committed.

Why not store handoff notes in CLAUDE.md or project memory?▼

CLAUDE.md and `.claude/memory/` are auto-loaded into every session, so task-specific notes there poison unrelated work. The brief lives in an opt-in location read only when you explicitly resume.

What happens if the repo changed between close and resume?▼

On resume, the skill re-reads every pointed-to file fresh, checks recent `git log`, and runs a basic functional check such as `just start` or `just build`. Any drift or breakage found is reported before new work begins.