devloglisted

# devlog A dev diary is only worth keeping if it's true and cheap. This skill makes it both: it reads what *actually happened* in git today across the user's repos and distills it into a short entry a human would enjoy rereading in six months. The entry is evidence-backed prose, not ceremony — and the daily commit it produces is a real contribution, because the diary content is real. ## Setup (first run only) Two paths, configured by editing this file — defaults: - **JOURNAL_REPO**: `~/Documents/GitHub/gitdiary` — the repo entries are committed to, as `entries/YYYY/MM/YYYY-MM-DD.md` - **REPOS_ROOT**: `~/Documents/GitHub` — the directory scanned for today's activity If JOURNAL_REPO doesn't exist on first run, offer to create it (a bare README + `entries/` is enough). ## Gather — evidence before prose For each git repo under REPOS_ROOT (top-level dirs; skip the journal repo itself): ```bash git -C <repo> log --since=midnight --author="$(git config user.name)" \ --all --oneline --no-merges ``` For repos with hits, go deeper: `git log --since=midnight --stat` for shape, and read the most significant diffs enough to describe them truthfully. Also worth capturing when present: current uncommitted work (`git status` — "WIP: half-done X" is honest diary material), and anything notable from the current session's own context (a bug chased for two hours that ended in a one-line fix is the *best* diary material and may not show in any diff). ## Write — the entry format `en