journal

mpazaryna's avatarfrom mpazaryna

Generates a journal entry from git commit history - just say "journal this" and I'll read the commits and write it up

⭐0stars🔀0forks📁View on GitHub🕐Updated Nov 26, 2025
[Developer Tools]

When & Why to Use This Skill

The Git Journal skill automates the transformation of raw git commit history into structured, meaningful development logs. By analyzing commit messages, file changes, and diff statistics, it helps developers maintain a chronological record of their technical decisions and progress, significantly reducing the manual overhead of project documentation and status reporting.

Use Cases

  • Daily Standup Preparation: Quickly generate a summary of the last 24 hours of work to provide clear, concise updates during team meetings.
  • Refactoring Documentation: Capture the evolution of complex code changes and the rationale behind specific architectural decisions during major refactors.
  • Project Onboarding: Create a readable history of a project's development for new team members to help them understand how the codebase has evolved over time.
  • Personal Work Reflection: Maintain a private developer journal to track personal productivity, technical challenges faced, and solutions implemented across different time ranges.
namejournal
descriptionGenerates a journal entry from git commit history - just say "journal this" and I'll read the commits and write it up

Git Journal

Generate a journal entry from your git history. Just say "journal this refactor" or "journal today's work" and I'll read recent commits and create a comprehensive entry.

Workflow

  1. Read Git Log - I analyze recent commits (you can specify time range)
  2. Generate Entry - I write a journal entry from the commit history
  3. Optional: Add Context - If you want to add insights beyond what's in the commits, tell me. Otherwise I'll work with what's there.
  4. Save - Write to docs/journal/YYYY-MM-DD-HHMM-slug.md

What Gets Captured

From git log:

  • Commit messages (the "what")
  • Changed files
  • Diff stats (lines added/removed)
  • Timestamps and authors

I infer and document:

  • Overall goal/theme of the work
  • Technical decisions visible in the commits
  • Progression and evolution of the work
  • Next steps based on commit patterns

Usage

Minimal:

  • "Journal this"
  • "Journal this refactor effort"
  • "Journal today's work"

With time range:

  • "Journal the last 4 hours"
  • "Journal since this morning"

With context (optional):

  • "Journal this. Key insight: we chose X over Y because..."

Requirements

  • Must be in a git repository
  • Must have commits in the time range (defaults to checking last 24 hours, shows recent commits)