From sessionlog
This skill should be used when the user asks to "recap", "brief me", "remind me", "what did we work on", "what happened last time", "catch me up on recent sessions", "sessionlog recap", "session recap", "recent session summary", "tldr sessions", or wants a quick summary of what was worked on in recent sessions for this project.
npx claudepluginhub florianbuetow/claude-code --plugin sessionlogThis skill uses the workspace's default tool permissions.
Read the last 3 session logs for this project and produce a concise TLDR of what was worked on.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Read the last 3 session logs for this project and produce a concise TLDR of what was worked on.
project_dir="$HOME/.claude/projects/$(pwd | sed 's|/|-|g')"
sessions=$(ls -t "$project_dir"/*.jsonl 2>/dev/null | head -4)
echo "$sessions"
We grab up to 4 because the most recent one is the current session. Skip it and use the 3 before it.
For each of the 3 previous sessions (skip the first/current one):
output_dir=$(mktemp -d)
sessions=$(ls -t "$project_dir"/*.jsonl 2>/dev/null | head -4 | tail -3)
for session_file in $sessions; do
sid=$(basename "$session_file" .jsonl)
"${CLAUDE_PLUGIN_ROOT}/scripts/export-session.sh" "$session_file" "$output_dir" "$sid"
done
echo "Exported to: $output_dir"
If fewer than 3 previous sessions exist, use however many are available.
Read the full content of each exported claude-<session-id>.txt file from the temp directory. Read them in reverse chronological order (most recent first).
You are summarizing recent work sessions for a developer returning to this project. Your goal is a quick, scannable recap — not a full continuity document.
Output format — print directly to the user (do NOT write to a file):
## Session Recap
Last time we worked on:
1. **<topic>** — <one-sentence summary of what was done and the outcome>
2. **<topic>** — <one-sentence summary>
3. **<topic>** — <one-sentence summary>
...
Rules:
rm -rf "$output_dir"