Our review
This skill prepares a handoff summary for a co-author or future session by reviewing git history, modified files, and pipeline status, then writing it to a dated file.
Strengths
- Automates gathering of key information (git log, changed files, pipeline status)
- Produces a structured, timestamped document under session_logs/
- Improves session continuity by capturing context and open questions
Limitations
- Relies on the quality and completeness of the git history
- Does not capture implicit context absent from code changes
- Requires access to a /status command for pipeline state
At the end of a work session or before a handoff, to summarize changes, regenerated outputs, and outstanding questions.
For quick informal notes without version control or when no pipeline status is available.
Security analysis
SafeThe skill performs read-only operations (git log, file listing, pipeline status) and writes a markdown summary to a local file. There are no destructive commands, no exfiltration, and no obfuscated payloads. The only side effect is creating a handoff document, which is benign.
No concerns found
Examples
Prepare a handoff summary for my next session. Check the git log since the last handoff, note recent file changes, and run /status. Save it to session_logs.Generate a co-author summary of what changed in the last 7 days, including regenerated outputs and open questions. Write it to a handoff file.Create a handoff document for my collaborator covering recent commits, modified files, pipeline status, and items to review.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.
KDoc Documentation Writer
Documentation
Writes concise KDoc documentation for Kotlin classes and functions, focusing on short summaries without metadata or variable documentation. Helps when adding KDoc to Kotlin files while skipping private or obvious members.