dev-diary
v1.0.0Keep a scannable developer journal that writes itself: discover a day's work from local Claude Code sessions, git commits, and prompt history; interview the user about what mattered and why; and record a tight, dated entry. Ships /dev-diary (write today) and /dev-diary-review (revise a past day). The journal is a separate private repo; this plugin is just the tool.
By Jordan RichlenLicense: MIT1 GitHub starsUpdated 2 hours ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Sep 24, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install dev-diary for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install dev-diary@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/JRichlen/agent-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/dev-diary/.
Plugin files
├── .claude-plugin/plugin.json├── skills/dev-diary/SKILL.md└── skills/dev-diary-review/SKILL.md
Included Skills2
Run a guided end-of-day loop that discovers everything the user did today from their local Claude Code sessions, git commits, and prompt history, interviews them about what actually mattered, and records a scannable dated entry in the dev-diary journal. Use this whenever the user wants to write a dev diary, daily log, work journal, standup note, changelog entry, or "what did I do today" wrap-up — or says things like "log today", "diary entry", "capture today", "end of day", "what did I get done", "dev-diary", or invokes /dev-diary. Also use it to backfill a past day (pass the date) or to review recent entries.
Open a past dev-diary entry and revise it with the user — correct mistakes, enrich a thin or backfilled day with the reasoning only they remember, tighten the writing, or re-pull the day's signals to check facts. Use whenever the user wants to edit, revise, amend, correct, fix, expand, or clean up an existing diary entry, review a backfilled day, or says things like "fix the 07-15 entry", "that day is wrong", "review my backfilled entries", "edit the diary", or invokes /dev-diary-review. This is the editing counterpart to /dev-diary (which writes today's entry); reach for it for any change to a day already on disk.
Plugin manifests1
{
"name": "dev-diary",
"version": "1.0.0",
"description": "Keep a scannable developer journal that writes itself: discover a day's work from local Claude Code sessions, git commits, and prompt history; interview the user about what mattered and why; and record a tight, dated entry. Ships /dev-diary (write today) and /dev-diary-review (revise a past day). The journal is a separate private repo; this plugin is just the tool.",
"author": {
"name": "Jordan Richlen"
},
"repository": "https://github.com/JRichlen/agent-plugins",
"homepage": "https://github.com/JRichlen/agent-plugins/tree/main/plugins/dev-diary",
"license": "MIT",
"keywords": [
"diary",
"journal",
"changelog",
"standup",
"dev-log",
"retrospective"
],
"skills": "./skills/",
"commands": "./commands/"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[dev-diary on Agent Plugins Marketplace](https://pluginsmp.com/plugins/dev-diary)