reflect

Reconstructs timelines from journals, git history, tasks and plans to recommend follow-up actions.

Updated Jun 10, 2026

Search Tags:#retrospective #handoff #git history #task tracking #takeaways #session review #journal analysis

Ready to run

npx skills add https://github.com/brewpirate/acme-frontier-ai --skill reflect-brewpirate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/brewpirate/acme-frontier-ai/tree/main/catalog/projects/field-notes/skills/reflect
Command: npx skills add https://github.com/brewpirate/acme-frontier-ai --skill reflect-brewpirate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns the end of a working session into a structured retrospective, helping you understand what happened, what mattered, and what to improve next time.

Core Features & Use Cases

Timeline reconstruction: Combines journal entries, commits, diffs, tasks, and plan status into a chronological narrative.
Session analysis: Identifies what went well, what was harder than expected, what was learned, and what should change.
Actionable follow-up: Produces suggested actions and future-session guidance for handoffs, debugging reviews, and long working sessions.

Quick Start

Use the reflect skill to review the current session’s journal, git history, task status, and active plan, then produce actionable takeaways for the next session.

Frequently Asked Questions about reflect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an actionable retrospective from git history and journal entries?▼

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.

What is the best way to create a handoff document from a long debugging session?▼

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.

Can I reconstruct a session timeline using TaskList and git diff stat?▼

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.

Does session review work with .claude/journal.jsonl files?▼

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.

How do I turn task tracking data and takeaways into future session guidance?▼

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.

What are the limitations of automated journal analysis for end-of-session reviews?▼

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.