devlog

Generate git journals and narrative devlogs from commit history.

1|Updated Sep 17, 2025
One-click install
npx skills add https://github.com/mpazaryna/agentic-factory --skill devlog-mpazaryna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devlog
Source: https://github.com/mpazaryna/agentic-factory/tree/main/pm/orchestra/skills/devlog
Command: npx skills add https://github.com/mpazaryna/agentic-factory --skill devlog-mpazaryna

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers document their work efficiently, whether it's summarizing code commits into a journal or writing narrative devlogs.

Core Features & Use Cases

  • Git Journal: Automatically generates a structured journal entry from recent git commit history.
  • Devlog: Assists in writing narrative documentation about development tasks, including context, decisions, and learnings.
  • Use Case: After a day of coding, you can ask Claude to "Journal this" to get a summary of your commits, or "Write a devlog about the auth refactor" to create detailed narrative documentation.

Quick Start

Ask Claude to "Journal this" to create a git journal entry.

Frequently Asked Questions about devlog

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

FAQPage Schema
How do I generate developer documentation from git commit history?

You can generate developer documentation from git commit history by processing recent commits to automatically create structured journal entries, summarizing daily work and technical decisions.

What is the best way to write a narrative devlog for a feature refactor?

Writing a narrative devlog involves structuring context, decisions, and learnings about a specific development task into detailed documentation, moving beyond simple commit messages to capture the full story.

Does generating a git journal require any specific command-line tools?

Generating a git journal requires git command-line tools to be installed, as the process directly accesses and parses your local commit history to structure the reporting output.

How do I document technical decisions for daily work using git?

Documenting technical decisions for daily work involves structuring commit history into daily work summaries, feature documentation, and technical decision logs to maintain a clear development record.

Can I create both structured journals and narrative documentation for the same code commits?

You can create both structured journals and narrative devlogs from the same code commits, allowing you to generate quick structured summaries or detailed narrative accounts of your development context and learnings.