Runs a standardized session handoff checklist updating memory, session journals, and repo state.
npx skills add https://github.com/mlorentedev/dotfiles --skill handoff-mlorentedev
Please help me install this Agent Skill. Skill: handoff Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/handoff Command: npx skills add https://github.com/mlorentedev/dotfiles --skill handoff-mlorentedev
## Session Handoff block in MEMORY.md, written via dotf mem handoff-write with per-thread sub-blocks keyed by git branch, so concurrent worktrees never clobber each other. - Session journal: Appends a durable session record under sessions/<date>-<project>-<agent>-<thread>.md with frontmatter and sections for context, work completed, decisions, and next actions. - Knowledge harvest and repo hygiene: Routes lessons, ADRs, runbooks, and troubleshooting entries to the right docs locations, reconciles GitHub project board status, prunes merged branches and worktrees, verifies artifacts, and triages pending PR reviews. - Use Case: At the end of a coding session spanning two worktrees and a merged PR, say "do handoff" to update the memory block, write the session journal, close out board items, prune stale branches, and record the single next action. ## Quick Start Say "do handoff" or "/handoff" at the end of your session to run the full handoff checklist and produce a summary with the next action.High-intent search queries and answers about installing and using this skill.
Invoke /handoff or say "do handoff" or "wrap up the session". The skill runs a fixed checklist: update the MEMORY.md continuity block, write the session journal, harvest lessons, reconcile the project board, verify repo state, and state one next action.
The continuity block holds one sub-block per thread, keyed by git branch and written via `dotf mem handoff-write`, which replaces only your thread. Session journal filenames include the thread from `dotf mem thread`, preventing same-day collisions between worktrees.
Skip when the session left no durable state: a quick question, a docs lookup, or a trivial single-line edit with nothing committed, no decision, and no open thread. If in doubt, run it anyway since a thin handoff is cheaper than a lost thread.
Yes. Thread resolution reads git's own on-disk state (HEAD and worktree gitdir files) with no tool-specific path patterns, so worktrees created by any agent or a bare `git worktree add` behave identically. The trigger lives in AGENTS.md for cross-agent use.
The checklist runs `dotf pr triage-queue`; if any PR awaits a disposition, you must run the PR review triage or post the review triage table before claiming the session finished. Unresolved reviewer findings cannot be left floating.
Soul-Brews-StudioCreate isolated Git worktrees for GitHub issue development.
MykhailoDmytriakhaLoad AGENTS.md, MEMORY.md, and session log to resume analytical work.
VitaDynamicsCreate sequentially numbered Architecture Decision Records in docs/adr/.
ippontechUpdate GitHub PR descriptions using git and session context.