session-handoff

Audit workspaces for junk files and update session documentation during handoffs.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Brennan-Wilkerson/second-brain-public --skill session-handoff-brennan-wilkerson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/Brennan-Wilkerson/second-brain-public/tree/main/.claude/skills/session-handoff
Command: npx skills add https://github.com/Brennan-Wilkerson/second-brain-public --skill session-handoff-brennan-wilkerson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-session workflows help you audit your workspace, validate adherence to development principles, update session documentation, and perform a structured handoff to teammates or next steps.

Core Features & Use Cases

  • Audit workspace for junk files in root directories, resolve version conflicts, and update session docs.
  • Run two workflows: Quick Handoff for a fast wrap and Full Handoff for a deep clean and thorough handoff.
  • Update .claude/sessions/CURRENT.md with a concise summary and archive the session as needed.

Quick Start

Say "quick handoff" to start the Quick Handoff Workflow. The assistant will scan the workspace, propose cleanup actions, and guide you through updating the session documentation. For a deeper cleanup, say "full handoff" to run the Full Handoff Workflow.

Frequently Asked Questions about session-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-of-session workspace cleanup and handoff?

Automate end-of-session handoffs by running a structured workflow that audits your workspace for junk files, resolves version conflicts, updates session documentation, and performs git operations. Use Quick Handoff for a fast wrap or Full Handoff for a deep clean across your development repository.

What's the best way to wrap up a development session with teammates?

Session handoff workflows validate adherence to development principles, archive session state, and update documentation in .claude/sessions/CURRENT.md with a concise summary. This structured approach ensures clean transitions between team members or next steps without manual auditing.

Can I automate version conflict resolution and junk file cleanup in git repositories?

Yes. The handoff workflow employs shell tooling (find, grep) and git operations to scan root directories for junk files, resolve version conflicts, and clean your repository. Two workflows support different cleanup depths: Quick Handoff for rapid wraps and Full Handoff for thorough validation.

How do I document and archive a development session?

The Full Handoff workflow updates your session documentation in .claude/sessions/CURRENT.md with a summary and archives the session state. This creates an auditable record of work completed and enables structured handoff to teammates or future work phases.

Do I need special setup to run workspace audits across software projects?

No special setup required. The handoff workflow applies to any development repository using standard shell tooling and git. It works across software projects and different repository structures to validate workspace cleanliness and prepare for session transitions.

When should I use Quick Handoff versus Full Handoff?

Use Quick Handoff for fast end-of-session wraps with basic cleanup and documentation updates. Use Full Handoff for thorough workspace audits, deeper conflict resolution, and comprehensive session archiving when transitioning to teammates or major project phases.