kramme:wrap-up-session

To document git status and session progress, use an end-of-session wrap-up workflow that audits uncommitted changes, summarizes accomplishments, extracts learnings, and records next steps for context preservation.

Detecting TODOs and WIP flags requires a session audit that scans recent changes for outstanding TODOs and work-in-progress signals like FIXME and XXX, then compiles them into a final report.

Create a repeatable wrap-up ritual by running a structured workflow with phased prompts for quality checks, context preservation, and learnings extraction to lock in project progress.

Yes, the wrap-up session skill works without external dependencies, running phased prompts natively to audit git status, detect TODOs, and generate a post-session summary.

Yes, you can preserve context and extract learnings after a daily work session by triggering optional learning extraction to capture insights and compile them into a concise wrap-up status report.

You should avoid an end-of-session wrap-up workflow when no code changes occurred, as the audit relies on detecting git status updates, untracked files, and stash state to summarize progress.