dev-journal

Generate structured Markdown journal entries from Git context.

2|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/rfhayn/forager --skill dev-journal-rfhayn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-journal
Source: https://github.com/rfhayn/forager/tree/main/.claude/skills/dev-journal
Command: npx skills add https://github.com/rfhayn/forager --skill dev-journal-rfhayn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps developers maintain a detailed, organized, and reflective journal of their work sessions. It ensures that crucial decisions, learnings, and AI tooling observations are recorded efficiently before every commit.

Core Features & Use Cases

  • Journal Entry Creation: Automatically generate and update the narrative session entry in a dedicated Markdown file.
  • Contextual Information: Pulls Git branch information and recent commits for the current context.
  • Entry Format: Offers a structured template to capture what happened, key decisions, learning, AI tooling observations, and what's next.

Quick Start

Write a new journal entry by saying, "update the journal" or "write a journal entry."

Frequently Asked Questions about dev-journal

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

FAQPage Schema
How do I track my software development sessions in Markdown?

Tracking software development sessions in Markdown involves generating structured journal entries that record key decisions, learnings, and what's next. This Skill automates session tracking by updating a dedicated Markdown file with your Git branch context.

How does Git integration work for development journaling?

Git integration for development journaling works by automatically pulling current branch information and recent commits into your entries. This contextual data grounds your session retrospectives and knowledge retention directly within your Git workflow.

What is the best way to capture AI tooling observations during a coding session?

Capturing AI tooling observations during a coding session is best handled using a structured journaling template. The template prompts you to record specific AI interactions alongside what happened and key decisions before committing your work.

Can I use session tracking for developer knowledge retention before every commit?

Yes, you can use session tracking for developer knowledge retention before every commit. The system is designed to ensure crucial decisions and learnings are recorded efficiently in Markdown format prior to finalizing Git commits.

Do I need any specific dependencies to maintain a structured development journal?

No specific dependencies are required to maintain a structured development journal. The system operates independently, utilizing standard Git commands and Markdown formatting to assist in session retrospectives without external components.