Session Handoff Summary

VerifiedSafe

Summarize project state: Git changes, modified files, pipeline status, and write a handoff report to session_logs.

Sby Skills Guide Bot
DocumentationBeginner
1708/14/2026
Claude Code
#session-handoff#git-log#handoff-summary#project-status

Recommended for

Our review

This skill creates a handoff summary by reviewing the Git log, recent file modifications, and current pipeline status, then writes a dated handoff file.

Strengths

  • Grounded in objective sources (git, recent files) to reduce oversights
  • Produces a structured, persistent file under session_logs/
  • Includes current pipeline status and open questions to ease resumption

Limitations

  • Relies on an up-to-date Git history for accuracy
  • Does not capture uncommitted context or issues not surfaced by /status
  • Not a substitute for in-depth design decision logs
When to use it

Use it at the end of a work session or before an interruption to prepare a smooth handoff for another agent or a future session.

When not to use it

Avoid using it when you only need a casual chat summary and do not require documented traceability in the repository.

Security analysis

Safe
Quality score85/100

The skill instructs to review git history, recent file modifications, and internal pipeline status, then write a summary to a local markdown file. There are no destructive commands, network calls, secret exfiltration, or safety bypasses. It only reads local repository state and writes within the project directory.

No concerns found

Examples

Standard handoff
Prepare a handoff summary and write it to session_logs/ with today's date.
Handoff for a new co-author
Create a session handoff for my teammate covering what changed since the last handoff and what to review.
Ongoing project status update
Run a handoff summary now, including open questions and the current pipeline status.

Prepare a co-author or future-session summary. Review: (1) Git log since the last handoff (or last 7 days if no prior handoff). (2) Any files modified recently. (3) Current pipeline status (run /status internally). Produce a plain-language summary covering: what changed, what outputs were regenerated, what to review, open questions. Write to session_logs/YYYY-MM-DD_handoff.md (create session_logs/ if needed).

Related skills