reflect

To generate an actionable retrospective from git history and journal entries, use a tool that reads your journal logs, git log, diff stats, and task statuses to reconstruct a chronological timeline and produce recommended follow-up actions.

Creating a handoff document from a long debugging session requires reconciling journal entries, git history, task statuses, and active plans to identify what was learned and suggest actionable future-session guidance for the next developer.

Yes, you can reconstruct a session timeline using TaskList and git diff stat by combining these data points with journal entries and active plan states to build a chronological narrative of your working session.

Session review works directly with .claude/journal.jsonl files by reading the journal entries alongside git log and task tracking data to analyze what went well, what was harder than expected, and what should change next time.

You turn task tracking data and takeaways into future session guidance by analyzing your task statuses, journal entries, and git history to identify what was learned and recommend specific actions for your next working session.

Automated journal analysis for end-of-session reviews relies entirely on reading .claude/journal.jsonl, git log, git diff stat, TaskList, and active plan state, meaning it cannot reconstruct sessions where these records are missing or incomplete.