Our review
Generates a handoff summary from recent git activity and pipeline status, saved to a dated markdown file.
Strengths
- Uses git history and status to capture context
- Produces a clear, structured summary
- Saves to session_logs for session continuity
Limitations
- Relies on the /status command being available
- Only captures the last 7 days if no prior handoff exists
- May miss context not represented in git or status
Use when wrapping up a session for a co-author or a future session.
Avoid when a real-time collaborative summary from live chat context is needed rather than git history.
Security analysis
SafeThe skill instructs reading git history, checking file modifications, and writing a summary file. It does not involve executing external scripts, exfiltrating data, or destructive commands.
No concerns found
Examples
Prepare a handoff summary for my co-author based on recent changes.Review the last week of changes and write a session log to session_logs.Check git log and status, then create a handoff note for future me.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).
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Move Documentation Files
Documentation
Automates moving documentation files with git history preservation, automatic alias injection, verification, and internal link updates.