Repository navigation
v1.1 — session-handoff skill
Adds
session-handoff
Manually-invoked skill that rescues critical session context to persistent auto-memory before /clear, /compact, or any conversation wipe.
The whole skill rides on one heuristic: would re-reading the repo recover this? If yes, drop. If no, it's a rescue candidate. That single test eliminates ~80% of false saves.
Highlights:
- Six rescue categories mapped to the
user/feedback/project/referenceauto-memory schema - Hard exclusions for secrets, code-derivable facts, git history, fixed-bug recipes, and CLAUDE.md duplicates — refused even when explicitly asked
- Pre-flight read of
MEMORY.mdto reuse slug prefixes, detect duplicates, and surface contradictions with stale entries - Review-before-write via
AskUserQuestion: multi-select for ≤ 4 candidates, table format for > 4, with explicit drop reasons shown - Conflict resolution that updates existing entries in place rather than writing duplicates
- Anti-patterns gallery (7 examples a senior engineer would refuse)
- Worked end-to-end example: 90-minute design session → 11 candidates → 6 keep, 5 drop, with the exact triage table
- Optional
UserPromptSubmithook (hooks/session-handoff-gate.js) that intercepts the first/clearand routes to the skill — second/clearpasses through
Install
npx skills add andreab67/agent-skills@session-handoff -g -yFull changelog
- 0ceff0a feat: add session-handoff skill — rescue critical context before /clear