Summarize session progress as a structured table of accomplished and pending steps. Invoke when the user asks for a "recap of the session", "review of the session", or "progress on the session".
Summarize session progress as a structured table of accomplished and pending steps. Invoke when the user asks for a "recap of the session", "review of the session", or "progress on the session".
metadata
{"version":"0.4.0"}
Session Recap
Steps
Establish the full session arc
If the full conversation is already available in your current context (the common case), use it directly as the session arc source — no separate transcript read is needed.
Otherwise, if running in an environment where session history must be read from an external transcript log:
Derive the transcript path: take {{VSCODE_TARGET_SESSION_LOG}}, replace debug-logs with transcripts, and append .jsonl
Run wc -l <path> in the terminal to check size
If < 500 lines: read the file directly
If ≥ 500 lines: run python3 <skill-dir>/scripts/recap.py <transcript-path> via terminal, where <skill-dir> is the directory containing this SKILL.md (derivable from the skill listing path). Use the script output as the session arc source instead of the raw file.
The session begins at the first user message — this is always the session.start invocation and is the guaranteed anchor for the start of the session
Build the complete session arc from that anchor to the current turn before enumerating steps