ck:journal

Summarize recent commits and session notes into Markdown journal entries.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-journal-quanganh208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:journal
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/journal
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-journal-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The journal skill reduces the friction of turning recent code changes, session memories, and meeting reflections into concise, persistent journal entries for project history and team knowledge.

Core Features & Use Cases

  • Automatic Journal Writing: Synthesize recent commits, code diffs, and session notes into short, focused journal entries highlighting key changes, impacts, and decisions.
  • Organized Output: Save entries to the project's documentation area to maintain an accessible changelog and reflection log; the skill recommends storing files in the docs/journals directory.
  • Collaboration Use Case: After a development session or sprint, generate 2–4 concise entries summarizing what changed, why it matters, and any follow-up actions for the team.

Quick Start

Ask the ck:journal skill to summarize the last 10 commits and session memories into three concise journal entries saved to the ./docs/journals/ directory.

Frequently Asked Questions about ck:journal

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

FAQPage Schema
How do I generate a changelog from recent commits and session notes?

To generate a changelog, synthesize recent commits and session notes into concise Markdown journal entries. These entries highlight key code changes, impacts, and decisions, saving directly into the project's documentation directory for accessible team history.

What is the best way to summarize code changes for team knowledge sharing?

Summarizing code changes for team knowledge involves creating persistent journal entries that analyze recent diffs and session reflections. This captures what changed, why it matters, and follow-up actions, reducing the friction of project handoffs.

How do I write sprint reflections from repository history and session memory?

Write sprint reflections by extracting key decisions and impacts from repository change history and session memory. The process synthesizes this data into 2–4 concise journal entries documenting development outcomes and follow-up team actions.

Do I need a specific directory structure to save project journals?

You need a designated directory to save project journals, with the recommended location being the docs/journals path. This organized output maintains an accessible changelog and reflection log within your existing project documentation area.

Can I automatically document commit history impacts and follow-up actions?

You can automatically document commit history by synthesizing recent code diffs and session notes into focused Markdown files. This process highlights key changes, why they matter, and any required follow-up actions for engineering workflows.