ck:journal

To automate journal reflections, this skill generates concise entries on recent changes and session insights. It captures decisions, impacts, and learnings, storing the output directly in your designated docs/journals directory.

Generating a change-log for a development session involves analyzing recent activity to capture decisions and impacts. This skill automates that process by creating reflective notes focused on your latest changes and storing them as structured journal entries.

Yes, frontmatter metadata is required for automated journal entries. This skill enforces specific frontmatter requirements, mandating name and description fields to ensure your generated reflections remain properly organized and documented.

You can use automated journaling for daily research review. This skill applies to research contexts by generating introspective notes that capture decisions, impacts, and learnings from your recent research sessions and activities.

Automated reflection notes are stored in the ./docs/journals/ directory. This ensures your generated journal entries and session change-logs are organized in a designated location for easy review and memory retention.

Automated journaling works without external dependencies. This skill operates independently using a built-in subagent to generate your reflections, requiring no additional frameworks or external components to process and store your session notes.