Skip to main content

handoff

End-of-session handoff — updates AGENTS.md and docs, 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.

Informations de source

Dépôt
webiny/data-transfer
Dernière activité de la source
30 juillet 2026 à 12:29
Langue détectée de SKILL.md
anglais
Étoiles
1
Forks
0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
name
handoff
description
End-of-session handoff — updates AGENTS.md and docs, 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/, __tests__/, projects/, templates/, docs/) - 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, public API, or doc index changed | | `docs/architecture.md` | Architecture patterns, DI, feature layout, or pipeline changed | | `docs/public-api.md` | Exports from src/index.ts were added/removed/changed | | `docs/project-structure.md`| Directory structure or file organization changed | | `docs/testing.md` | Testing patterns or conventions changed | | `docs/hard-won-decisions.md`| A significant design decision was made | State which docs you updated and which you skipped (with reason). ## Step 3 — Run checks ``` yarn format:fix && yarn lint:fix && yarn check:imports && yarn ts-check && yarn test ``` Fix any issues. If tests fail, investigate and fix before proceeding. ## Step 4 — Commit all changes Commit everything that's uncommitted. Use a descriptive message. ## Step 5 — Write handoff file Write `docs/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 and test count ## Key decisions - Any rules established or changed - Any architectural decisions made - Any conventions introduced ## Current state - Branch: <branch name> - Tests: N passed - Typecheck: 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) - All checks green: format, lint, imports, typecheck, N tests - <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."
Voir sur GitHub