agentleFS
kev1nzh37kev1nzh37/handoff/CLAUDE.md

handoff

CLAUDE.md0 starsChanged 4 months agoMITView on GitHub

Use the Handoff workflows in skills/handoff/SKILL.md, skills/handon/SKILL.md, and skills/handoff-handon/SKILL.md. When the user says /handoff, "handoff", "prepare a handoff", or indicates they are ending a work session: When the user says /handon, "handon", "continue from last time", or asks to restore context: Never write secrets, credentials, .env values, private keys, or production configuration into handoff files.

  • Reads credentials

The file

We split this CLAUDE.md into the rules it gives an agent

9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the Handoff workflows in skills/handoff/SKILL.md, skills/handon/SKILL.md, and skills/handoff-handon/SKILL.md.

    line 3
  2. Very specific:

    When the user says /handoff, "handoff", "prepare a handoff", or indicates they are ending a work session:

    line 5
  3. Very specific:

    Follow the Handoff workflow.

    line 8
  4. Very specific:

    Update docs/HANDOFF/TODO.md only when the task list changed or new follow-up work was discovered.

    line 10
  5. Very specific:

    Update docs/HANDOFF/DECISIONS.md only when a durable project decision was made or confirmed.

    line 11
  6. Very specific:

    When the user says /handon, "handon", "continue from last time", or asks to restore context:

    line 13
  7. Distinctive:

    Follow the Handon workflow.

    line 16
  8. Distinctive:

    Do not modify code until the user explicitly confirms.

    line 18
  9. Very specific:

    Never write secrets, credentials, .env values, private keys, or production configuration into handoff files.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “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
CLAUDE.md

Handoff

Use the Handoff workflows in skills/handoff/SKILL.md, skills/handon/SKILL.md, and skills/handoff-handon/SKILL.md.

When the user says /handoff, "handoff", "prepare a handoff", or indicates they are ending a work session:

  1. Read skills/handoff-handon/SKILL.md.
  2. Follow the Handoff workflow.
  3. Always update docs/HANDOFF/CURRENT.md.
  4. Update docs/HANDOFF/TODO.md only when the task list changed or new follow-up work was discovered.
  5. Update docs/HANDOFF/DECISIONS.md only when a durable project decision was made or confirmed.

When the user says /handon, "handon", "continue from last time", or asks to restore context:

  1. Read skills/handoff-handon/SKILL.md.
  2. Follow the Handon workflow.
  3. Summarize the restored context first.
  4. Do not modify code until the user explicitly confirms.

Never write secrets, credentials, .env values, private keys, or production configuration into handoff files.

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.