Skip to main content

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.

Datos de origen

Repositorio
webiny/data-mock
Última actividad en el origen
4 de septiembre de 2026 a las 10:12
Idioma detectado de SKILL.md
inglés
Estrellas
1
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
handoff
description
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 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: ```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 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."
Ver en GitHub