session-handofflisted

Generate a structured handoff document at the end of a work session — what was implemented, which decisions were made and why, open questions, and recommended next steps. The document is written to `outputs/handoffs/latest.md`, and the previous handoff is rotated to a dated, topic-named archive (repo convention, cf. `branch-review`). Use this skill whenever the user wants to end a session, create a handoff, or says: "session-handoff", "wrap up", "end of session", "session summary", "hand over to next session", "Handoff erstellen", "Session abschließen", "was haben wir heute gemacht", "Zusammenfassung der Session", "nächste Schritte dokumentieren", "übergib an nächste Session".
lx-wnk/skills · ★ 1 · AI & Automation · score 71

Install: claude install-skill lx-wnk/skills

# Session Handoff Generate a structured handoff document at `outputs/handoffs/latest.md` at the end of a work session. Goal: the next session (or another developer) can pick up exactly where this one left off without reconstructing context from scratch. **Language:** the handoff content follows the language of the user's request (English request → English handoff, German request → German handoff). Commit messages and code stay in their original language. **Output path:** the current handoff is always `outputs/handoffs/latest.md`; on each run the previous `latest.md` is rotated to a dated, topic-named archive under `outputs/handoffs/` (see Step 3). `outputs/` should be `.gitignore`-d at repo level; that is the repo's responsibility, not this skill's. ## Examples ```bash # Simple handoff without arguments /session-handoff # With an optional focus hint /session-handoff Focus: Auth refactoring and new API endpoints # With a time hint (overrides the default heuristic) /session-handoff since Monday ``` ## Step 1: Determine the session boundary The session boundary decides which commits land in the handoff. Resolution order: 1. **Conversation context first.** You know from this conversation when the session started — use that knowledge primarily. Example: "we started with the auth refactor today" → only commits from the first refactor commit onward. 2. **`$ARGUMENTS` time hint** (if present): "since Monday", "last 2 days", "today" → translate into `--since="..."`. 3. **Fal