skills.rest
hidonguyen
hidonguyenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ck:journal

Write journal entries analyzing recent code changes and session reflections.

Updated Apr 2, 2026
Search Tags:#changelog#documentation#journal#reflection#summarize#developer-workflows
One-click install
npx skills add https://github.com/hidonguyen/trade-ops --skill ck-journal-hidonguyen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:journal
Source: https://github.com/hidonguyen/trade-ops/tree/main/.opencode/skills/journal
Command: npx skills add https://github.com/hidonguyen/trade-ops --skill ck-journal-hidonguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a fast, consistent way to capture recent code changes, session reflections, and key decisions as concise journal entries to maintain project history and reduce manual note-taking.

Core Features & Use Cases

  • Automated Journaling: Uses the journal-writer subagent to analyze recent repository changes and session memory to produce focused entries.
  • Repository Documentation: Saves entries to the docs/journals/ directory so teams can track changes, rationale, and impacts over time.
  • Organized Outputs: Recommends invoking the /ck:project-organization skill to structure and index journal entries for discoverability.
  • Use Case: After a development session or a set of commits, generate a short entry summarizing what changed, why it mattered, and any follow-up tasks.

Quick Start

Write a concise journal entry summarizing recent repository changes, key decisions, and session reflections and save it to docs/journals/.

Frequently Asked Questions about ck:journal

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

FAQPage Schema
How do I generate changelog entries from recent code changes?▼

To generate changelog entries from recent code changes, the skill analyzes repository history and session memory to produce concise journal entries documenting what changed, why it mattered, and any follow-up tasks.

What is the best way to automate developer journaling after a sprint?▼

Automated developer journaling after a sprint uses a subagent to analyze session reflections and commits, saving focused summaries to a designated documentation directory to maintain project history without manual note-taking.

Can I use session memory to write sprint retrospectives?▼

Yes, you can use session memory to write sprint retrospectives by processing recent code changes and key developer decisions into structured journal entries suitable for team documentation workflows.

Does the journaling process require access to repository change history?▼

Yes, the journaling process requires access to repository change history and session context to accurately analyze recent commits and translate them into structured documentation entries.

How do I organize generated journal entries for team discoverability?▼

To organize generated journal entries for team discoverability, the skill recommends invoking a project organization skill to structure and index the saved files within the documentation directory.

Related Skills

Explore More Software Engineering Skills→
DatTran26DatTran26

ck:journal

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

Community
Basic
joonlabjoonlab
8

note-save

Standardize markdown knowledge storage with frontmatter injection and llms.txt index updates.

Community
Advanced
bacocobacoco
2

cortex

Trace file changes and commits to generate Cortex session memory files.

Community
Advanced
cardmagiccardmagic

notes

Search, read, create, and delete Apple Notes via the notes CLI.

Community
Intermediate