agentleFS
Sign inStart free
surasakchosurasakcho/claude-skills/handoff/SKILL.md

handoff

Skill0 starsChanged 5 months agoMITView on GitHub

Summarise the session and write next-session notes into a committed project file, then commit and push so the handoff is available on any machine.

191 other projects use a version of this, 80 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-ts-deep-modules, to-questionnaire and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • AWSSkill

    to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    Also in 93 projects that use this

  • AWSSkill

    wait-what

    Stop. That last message did not land: re-pitch it.

    Also in 112 projects that use this

  • ryotaroh180105Skill

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 41 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look for an existing file to append to, in this order:

    line 12
  2. Very specific:

    If none exist, create HANDOFF.md in the project root.

    line 17
  3. Very specific:

    Add or update a ## Next Session section at the top of the file (after any title/header).

    line 21
  4. Distinctive:

    Do not duplicate content already captured in commits, PRDs, or ADRs — reference them by path or URL instead.

    line 28
  5. Distinctive:

    If the user passed arguments, treat them as a description of what the next session will focus on and tailor the note accordingly.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 172 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Close out the current session by writing a handoff note into a tracked project file and pushing it. The note must travel with the repo — never save it to OS temp or claude memory.

1. Find or create the handoff target file

Look for an existing file to append to, in this order:

  • CONTEXT.md (preferred if it exists)
  • HANDOFF.md
  • TODO.md

If none exist, create HANDOFF.md in the project root.

2. Write the handoff note

Add or update a ## Next Session section at the top of the file (after any title/header). Keep it concise — bullets, not prose. Include:

  • What was done this session — one sentence max, just enough context.
  • What to do next — specific actionable items, ordered by priority.
  • Known bugs or blockers — anything that will bite the next session immediately.
  • Suggested skills — if a specific Claude Code skill would help (e.g. /run, /tdd), name it.

Do not duplicate content already captured in commits, PRDs, or ADRs — reference them by path or URL instead.

Redact any sensitive information (API keys, passwords, PII).

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the note accordingly.

3. Commit and push

Stage only the handoff file. Commit with a short message like docs: handoff notes for next session. Push to the current branch's upstream.

4. Report back

Confirm: what file was written, what was committed, and that it pushed — so the user knows the notes are safe on the remote.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free