skills.rest
MinhHoangDono
MinhHoangDonoCOMMUNITY
Explore all skills by this author →
GitHub

ck:journal

Convert recent development context into concise journal entries in ./docs/journals/.

Updated Mar 7, 2026
Search Tags:#journal#decision tracking#reflection#change log#engineering notes#memory review
One-click install
npx skills add https://github.com/MinhHoangDono/antigravity-kit --skill ck-journal-minhhoangdono
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:journal
Source: https://github.com/MinhHoangDono/antigravity-kit/tree/main/.agent/skills/journal
Command: npx skills add https://github.com/MinhHoangDono/antigravity-kit --skill ck-journal-minhhoangdono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of forgetting key decisions, changes, and reflections from recent work by turning them into concise, structured journal entries.

Core Features & Use Cases

  • Change and memory reflection: Leverages a journal-writer subagent to review memories and recent code changes to ground the entry in real context.
  • Concise, decision-focused writing: Produces brief entries centered on the most important events, impacts, and decisions.
  • Consistent storage location: Keeps journal output organized in the ./docs/journals/ directory.

Quick Start

Use the ck:journal skill to write a short reflection about your latest session and changes.

Frequently Asked Questions about ck:journal

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

FAQPage Schema
How do I track engineering decisions and changes after a development session?▼

To track engineering decisions and changes, you can generate concise journal entries that document key events, decisions, and impacts from your recent development context. This helps maintain a structured engineering log over time.

What is the best way to maintain an engineering log for memory review?▼

Maintaining an engineering log involves converting recent development context into concise, structured journal entries. This approach centers on important events and decisions, keeping your progress organized for later memory review.

Can I automatically generate a change log from my recent code changes?▼

Yes, you can generate a change log by using a journal-writer subagent to explore relevant memories and recent code changes. It grounds the output in real context and writes the results into a specific directory.

Where are the generated journal entries stored?▼

Generated journal entries are stored consistently in the ./docs/journals/ directory. This ensures your engineering notes and decision tracking remain organized in a predictable location for future access.

Do I need a specific subagent to write reflection notes?▼

Yes, writing reflection notes requires using a journal-writer subagent. This subagent explores relevant memories and code changes to ground the concise, decision-focused journal entry in real development context.

Related Skills

Explore More Content & Communication Skills→
mpazarynampazaryna
1

journal

Generate markdown journal entries from git commit history.

Community
Basic
DatTran26DatTran26

ck:journal

Generate concise journal entries analyzing recent changes and session reflections for software projects.

Community
Basic
aliyehiawialiyehiawi

journal

Log daily journal entries with YAML frontmatter and path-based wiki-links.

Community
Advanced
tomwangowatomwangowa
1

work-log-analyzer

Parse Markdown work logs to track TODOs, decisions, and timeline events.

Community
Intermediate