How do I install the Handoff skill?

Run npx skillmds@latest add webiny/handoff in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Handoff safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Handoff?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Handoff free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Handoff?

webiny (@webiny) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Handoff by webiny — Agent Skill

Name: Handoff
Author: webiny

Handoff

End-of-session handoff — updates AGENTS.md, writes a session handoff file, and generates a copy/paste prompt for the next agent. Use when user says "handoff", "wrap up", "end session", "clear context", or wants to prepare context for the next conversation.

webiny d82c593 2.9 KB Updated Sep 17, 2026

File contents

Session Handoff

Run all steps in order. Do not skip any.

Step 1 — Discover what changed

Run these commands and study the output:

git log --oneline origin/main..HEAD
git diff --stat origin/main..HEAD

If origin/main is not set, use the oldest commit of the session (check conversation context for the starting commit).

Summarize:

How many commits
Which areas changed (src/, .claude/, documentation/, etc.)
Key features/fixes/refactors

Step 2 — Update project docs

For each doc below, check if this session's changes require an update. Only touch docs that are actually stale — don't rewrite for the sake of it.

Doc	Update if...
`AGENTS.md`	Key rules, project structure, or file reading rules changed
`CLAUDE.md`	Project-level instructions changed
`documentation/plans/*.md`	Plan progress changed (tasks completed, blocked, etc.)

State which docs you updated and which you skipped (with reason).

Step 3 — Run checks

Run whatever checks are configured in package.json scripts:

yarn lint && yarn format:check && yarn compile

Fix any issues. Format with yarn format:fix if needed.

Step 4 — Commit all changes

Commit everything that's uncommitted. Use a descriptive message.

Step 5 — Write handoff file

Write documentation/handoff/YYYY-MM-DD-<slug>.md where <slug> is a 2-3 word kebab-case summary of the session's main work.

Template:

# Session Handoff — YYYY-MM-DD — <Title>

## What was done

- Bullet list of significant changes (not every commit — group by theme)
- Include commit count

## Key decisions

- Any rules established or changed
- Any architectural decisions made
- Any conventions introduced

## Current state

- Branch: <branch name>
- Build: passing/failing
- Unpushed commits: N

## What might come next

- Obvious follow-up work
- Known issues or loose ends
- Anything the user mentioned wanting to do next

Step 6 — Generate handoff prompt

Output a fenced block the user can copy/paste into the next conversation. Format:

```
## Context — Session YYYY-MM-DD handoff

<2-3 sentence summary of what was accomplished>

### Key changes
- <grouped bullet list of what changed, with file/area references>

### Rules established
- <any new conventions or rules, with enough detail to act on>

### Current state
- Branch: <name>, N commits ahead of origin (not pushed)
- <any caveats>

### What might come next
- <prioritized list of follow-up work>
- <known issues>
```

Tell the user: "Copy the block above and paste it as your first message in the next conversation."

---name: handoffdescription: End-of-session handoff — updates AGENTS.md, writes a session handoff file, and generates a copy/paste prompt for the next agent. Use when user says "handoff", "wrap up", "end session", "clear context", or wants to prepare context for the next conversation.---# Session HandoffRun all steps in order. Do not skip any.## Step 1 — Discover what changedRun these commands and study the output:```git log --oneline origin/main..HEADgit diff --stat origin/main..HEAD```If `origin/main` is not set, use the oldest commit of the session (check conversation context for the starting commit).Summarize:- How many commits- Which areas changed (src/, .claude/, documentation/, etc.)- Key features/fixes/refactors## Step 2 — Update project docsFor each doc below, check if this session's changes require an update. Only touch docs that are actually stale — don't rewrite for the sake of it.| Doc | Update if... || --- | --- || `AGENTS.md` | Key rules, project structure, or file reading rules changed || `CLAUDE.md` | Project-level instructions changed || `documentation/plans/*.md` | Plan progress changed (tasks completed, blocked, etc.) |State which docs you updated and which you skipped (with reason).## Step 3 — Run checksRun whatever checks are configured in `package.json` scripts:```yarn lint && yarn format:check && yarn compile```Fix any issues. Format with `yarn format:fix` if needed.## Step 4 — Commit all changesCommit everything that's uncommitted. Use a descriptive message.## Step 5 — Write handoff fileWrite `documentation/handoff/YYYY-MM-DD-<slug>.md` where `<slug>` is a 2-3 word kebab-case summary of the session's main work.Template:```markdown# Session Handoff — YYYY-MM-DD — <Title>## What was done- Bullet list of significant changes (not every commit — group by theme)- Include commit count## Key decisions- Any rules established or changed- Any architectural decisions made- Any conventions introduced## Current state- Branch: <branch name>- Build: passing/failing- Unpushed commits: N## What might come next- Obvious follow-up work- Known issues or loose ends- Anything the user mentioned wanting to do next```## Step 6 — Generate handoff promptOutput a fenced block the user can copy/paste into the next conversation. Format:```````## Context — Session YYYY-MM-DD handoff<2-3 sentence summary of what was accomplished>### Key changes- <grouped bullet list of what changed, with file/area references>### Rules established- <any new conventions or rules, with enough detail to act on>### Current state- Branch: <name>, N commits ahead of origin (not pushed)- <any caveats>### What might come next- <prioritized list of follow-up work>- <known issues>```````Tell the user: "Copy the block above and paste it as your first message in the next conversation."

Frequently asked questions