session-handoff
Use when context window is nearly exhausted and unfinished work must resume in a fresh session without losing progress, re-asking settled questions, or re-introducing fixed bugs.
- License 许可
- MIT
- 最近更新
- 2026-10-05
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- session-handoff
- description
- Use when context window is nearly exhausted and unfinished work must resume in a fresh session without losing progress, re-asking settled questions, or re-introducing fixed bugs.
03 SKILL.md 正文
Session Handoff
Overview
A handoff file lets the next session resume exactly where this one stopped. Its only job: verified facts + the single next action.
When to Use
- Context usage is high (>80%) with unfinished work (uncommitted changes, failing gate, mid-plan task).
- When NOT to use: everything committed, gate green, nothing in flight.
The Contract
Exactly these sections, in order. Nothing else.
- State (verified, not remembered): branch, last 3–5 commits (
git log --oneline), working tree (git status --short), sync vs base (git log origin/main..HEAD --oneline,git branch -r --contains HEAD). Paste outputs. - In-flight work: each item with
file:line, DONE vs REMAINS, exact next command. - Open issues: marked OBSERVED (saw it fail) or HYPOTHESIZED (suspect it).
- Hard rules: max 3 lines, copied verbatim from the repo instruction file.
- Resume pointer: plan/tracking file path if one exists.
Rules
- Evidence before prose. Claims come from just-run commands; otherwise mark
[UNVERIFIED]. - No invented design. Unknowns stay
UNKNOWN:— never filled in to "be helpful". - No session-meta leakage. Project state only; never mention this skill, the process, or any experiment.
- Confidence labels (
[VERIFIED]/[ASSUMED]/[UNVERIFIED]) on factual claims, not on instructions or headers. - One next action. A single concrete step, not a menu.
Rationalizations (observed in baseline — reject all three)
| Excuse | Reality |
|---|---|
| "More detail is safer" | Unverified detail becomes false instructions. |
| "Summary needs no commands" | Memory lies about git state. Paste output or label [UNVERIFIED]. |
| "One process note helps" | Meta-notes leak across sessions. Project state only. |
Common Mistakes
| Mistake | Fix |
|---|---|
| Git state from memory | Run the commands, paste outputs |
| Vague resume ("open and see") | file:line + done-vs-remaining + next command |
| Reworded repo rules | Copy the 3 lines verbatim |
Red Flags — STOP and rewrite
- Implementation detail with no prior decision behind it
- Any sentence about this skill, session, or experiment
- Git claim without pasted command output
- Missing label where one is needed
- More than one next step
04 同仓库更多 Skills
tiptap-prosemirror-best-practices
Best practices and architectural standards for integrating TipTap, ProseMirror, Tailwind Typography, and Supabase autosave in Flow State. Use whenever creating, modifying, or debugging rich text editors, task lists, and real-time autosave.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback