create-devlog

Generate a devlog entry summarizing recent commits or working-tree changes.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill create-devlog-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-devlog
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/create-devlog
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill create-devlog-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent development logs after coding sessions is tedious and often skipped, leaving teams without a record of what changed and why. This Skill automates the creation of structured devlog entries from git history or uncommitted changes. ## Core Features & Use Cases - Commit Summarization: Summarize the last commit, the last N commits, or uncommitted working-tree changes into a structured devlog. - Standardized Frontmatter: Generates YAML frontmatter conforming to a universal artifact schema, including commit hashes and optional run IDs linking to orchestrated runs. - Ticket-Aware Saving: Automatically resolves session context to save the devlog under the correct ticket or project directory with a timestamped filename. - Use Case: After finishing a bug fix across three commits, invoke the Skill with the argument 3 to produce a devlog capturing the problem, solution, and lessons learned, saved to the ticket's artifact directory. ## Quick Start Ask the agent to create a devlog summarizing the last 3 commits and save it to the current ticket's artifact directory.

Frequently Asked Questions about create-devlog

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

FAQPage Schema
How do I create a devlog from recent git commits?

Invoke the create-devlog skill with no argument to summarize the last commit, or pass a number to summarize the last N commits. The skill reads git log output, composes a structured entry, and saves it with timestamped frontmatter.

How do I document uncommitted changes in a devlog?

Pass the working-tree argument to summarize uncommitted changes instead of commits. In this mode the commits field is omitted from the frontmatter since there is no commit history to reference.

Where are devlog files saved?

Devlogs are saved under the artifact base directory resolved by the session-context deriver. Ticket branches produce ticket-scoped paths, while branches without a ticket prefix fall back to a project-scoped devlogs directory.

What frontmatter does a devlog entry include?

The frontmatter follows a universal artifact schema plus devlog-specific fields such as commit hashes and an optional run ID. It is generated by a resolve-frontmatter shell script and prepended verbatim to the markdown body.

Why does my devlog path contain tickets/null?

This happens when a null ticket ID is interpolated into the path instead of triggering the fallback. Branches without a recognizable ticket prefix return a null ticket ID, which must be treated as no ticket and routed to the project-scoped fallback path.