dev-diary-reviewlisted

# Dev Diary — Review & Edit Revise a day that's already written. The entry exists; the job now is to make it *truer* — fix what's wrong, add the judgment only the user carries in their head, or sharpen the prose — without losing what's already good. Editing is not rewriting: preserve every bullet that still holds. The journal lives in the separate private repo `~/projects/dev-diary`; entries are at `entries/<YYYY>/<YYYY-MM-DD>.md`. ## The loop ### 1. Pick the entry - If a date was given, edit `~/projects/dev-diary/entries/<YYYY>/<date>.md`. If that file doesn't exist, say so and offer to write it fresh with `/dev-diary <date>`. - If no date, show a short menu of recent entries so the user can choose. The fastest source is the changelog spine: ```bash sed -n '1,15p' ~/projects/dev-diary/CHANGELOG.md ``` or list files: `ls ~/projects/dev-diary/entries/*/ | tail`. Ask which day. ### 2. Load what's there — and, if useful, re-check the facts - Read the current entry in full. This is your baseline; you are amending it. - When the edit is about accuracy (not just wording), re-pull the day's signals so you're correcting against evidence, not guessing: ```bash ~/projects/dev-diary/skills/... # NOT here — the script ships in this plugin: <this-plugin>/skills/dev-diary/scripts/discover-today.sh <date> ``` (The discovery script lives beside the sibling `dev-diary` skill: `../dev-diary/scripts/discover-today.sh`.) Drill into a commit with `git -C ~/proje