journal

To summarize code changes for a development retrospective, you can generate structured journal entries that capture key decisions and learnings from your recent sessions. This Skill automates that process by recording recent code changes into a structured journal.

Maintaining session reflections involves recording insights and changes systematically. This Skill captures session reflections and stores them as structured journal entries in a dedicated directory, preserving memory and aiding project onboarding.

To create a journal entry summarizing today's work, you use the journal-writer subagent. It processes your recent changes and session reflections, generating a structured summary stored under the ./docs/journals/ directory.

Generated journal entries are stored under the ./docs/journals/ directory. This organized storage approach ensures quick access for later review, onboarding, and software development knowledge capture.

Yes, you can use topic hints to guide the organization of your code change summaries. The journal-writer subagent supports topic-based organization to accelerate knowledge capture and systematically structure your reflections.