jrichlen/dev-diary
Keep a scannable developer journal that writes itself: discover the day's work from sessions, commits and prompts, interview the user, record a dated entry. Ships /dev-diary and /dev-diary-review.
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.