dev-diarylisted
Install: claude install-skill JRichlen/claude-plugins
# Dev Diary
Turn a day of scattered work into one entry that a busy person can scan in
fifteen seconds and a future self can trust. The value is not transcription —
the raw signals already exist. The value is **judgment**: separating the two or
three things that mattered from the noise, and recording *why* they mattered.
This skill ships in the `dev-diary` plugin, but the **journal itself is a
separate private repo at `~/projects/dev-diary`**. Entries are committed there,
organized temporally under `entries/YYYY/`. Keeping the tool (this plugin) and
the journal (that repo) apart is deliberate: the plugin is shareable; the diary
is private.
## The loop
Work through these phases in order. Do not skip the interview — an unreviewed
auto-summary is exactly the low-signal artifact this skill exists to avoid.
### 1. Resolve the day and locate the repo
- Target date = the argument if given, else today in **local** time
(`date +%F`). The user's clock is what defines "today", not UTC.
- The journal root is `~/projects/dev-diary` (a separate private repo from this
plugin). Confirm `entries/` exists there.
### 2. Discover — run the deterministic first pass
Run the discovery script and read its digest. It is fast, read-only, and
gathers the three signals that actually show what happened:
```bash
<skill-dir>/scripts/discover-today.sh [YYYY-MM-DD]
```
It emits Markdown with three sections: **Prompts typed** (from
`~/.claude/history.jsonl`), **Sessions active** (titles + turn c