agentleFS
Sign inStart free
kev1nzh37kev1nzh37/handoff/skills/handon/SKILL.md

handon

Skill0 starsChanged 4 months agoMITView on GitHub

Run the `/handon` workflow for the current repository. Use when the user says `/handon`, "handon", "continue from last time", "restore context", or asks to resume work from repo-local handoff files without relying on prior chat history.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. SuShuheng/making-things★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read these files when present:

    line 12
  2. Very specific:

    If docs/HANDOFF/CURRENT.md is missing, say exactly:

    line 32
  3. Very specific:

    If the user expected cross-machine continuity, remind them that /handoff writes repo-local files only.

    line 45
  4. Very specific:

    If the current branch differs from the branch recorded in CURRENT.md, stop and ask for confirmation before modifying files.

    line 49
  5. Distinctive:

    If local uncommitted changes exist, say that local uncommitted changes were detected and summarize first.

    line 51
  6. Distinctive:

    Keep the first response brief.

    line 55
  7. Distinctive:

    When responding in Chinese, end with the natural equivalent of "we can continue now."

    line 68
  8. Distinctive:

    Wait for explicit confirmation such as "start", "continue", or "go ahead" before modifying code.

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Handon

Restore project context from repo-local handoff files. Do not modify code during the first response.

Read First

Read these files when present:

AGENTS.md
docs/HANDOFF/CURRENT.md
docs/HANDOFF/DECISIONS.md
docs/HANDOFF/TODO.md
README.md

Then check:

git status
git branch --show-current
git log --oneline -5

Missing Handoff

If docs/HANDOFF/CURRENT.md is missing, say exactly:

No handoff file found.

Expected:
docs/HANDOFF/CURRENT.md

Handon cannot restore the previous project state from handoff.

You may infer context from README, git log, and TODO only after clearly labeling it as inference.

If the user expected cross-machine continuity, remind them that /handoff writes repo-local files only. The previous machine must commit and push docs/HANDOFF/ or otherwise sync those files before /handon can restore context here.

Branch Or Local Changes

If the current branch differs from the branch recorded in CURRENT.md, stop and ask for confirmation before modifying files.

If local uncommitted changes exist, say that local uncommitted changes were detected and summarize first. Do not modify files until the user confirms.

Response Format

Keep the first response brief. Return one compact summary, optional next steps, and a warm continue cue:

I read the handoff. We are currently [one-sentence objective]. Last time, [one-sentence completed work]. The main remaining point is [one-sentence blocker/risk/next task].

Next:
1. ...
2. ...
3. ...

Ready to continue.

When responding in Chinese, end with the natural equivalent of "we can continue now."

Mention local uncommitted changes in one short sentence when present. Include key file names only when they are necessary for the next action.

Wait for explicit confirmation such as "start", "continue", or "go ahead" before modifying code.

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