claude-daily-retro
A nightly continuous-improvement retrospective for Claude Code.
Every evening it reviews everything that happened across all of that day's Claude
sessions — every correction, interruption, repeated instruction, rework loop, and
win — then runs a 3-lens "council" over each one (like a scrum retro) and turns the
top findings into new/improved skills and CLAUDE.md rules — with a dedup gate so
it improves what already exists instead of piling up duplicates.
It's the loop that makes your Claude setup get better while you sleep.
What it does (3 steps)
- Gather — reads your local session transcripts (
~/.claude/projects/*/*.jsonl)
- built-in memory across all projects for the target day, and writes a flat,
non-judgmental list of everything that happened →
~/.claude/retro/<date>/01-events.md.
- Council — 3 parallel sub-agent lenses (Historian / Root-cause / Action-engineer)
analyze every event: what / why / how to respond / how to prevent / what to build →
02-council.md.
- Act — ranks the top 3, runs a dedup gate (improve existing, never duplicate),
and either:
- apply mode → auto-edits global
~/.claude/CLAUDE.md (in a demarcated
auto-section it never lets itself overwrite your hand-written rules), bumps
~/.claude/IMPR-CHANGELOG.md, updates a registry; or
- propose mode → writes recommendations to
03-proposals.md and changes nothing.
Runs unattended via a scheduler (macOS launchd / Linux cron) at a time you pick, with a
7-day catch-up so a powered-off evening isn't lost.
Reliability: the wrapper is rate-limit aware — if the nightly run dies on a usage/session
limit it parses the advertised reset time, waits (bounded), and retries up to 3×. Step outputs
carry a completion sentinel, so a retry resumes at the step that died instead of redoing the
whole retro. A lock dir prevents overlapping runs (RunAtLoad + schedule + manual).
No --dangerously-skip-permissions. It runs headless with --permission-mode acceptEdits
and an explicit tool allowlist.
Install
Option A — the wizard (skill and scheduler, recommended)
git clone https://github.com/LynchzDEV/claude-daily-retro.git
cd claude-daily-retro
./install.sh
The wizard asks you to choose: apply vs propose mode, run time, catch-up depth,
whether to seed history skip-markers, and the scheduler backend. Re-run it any time to
change settings. Uninstall with ./uninstall.sh.
Option B — Claude Code plugin (skill only, cross-platform)
/plugin marketplace add LynchzDEV/claude-daily-retro
/plugin install daily-retro@lynchzdev
Gives you the /daily-retro skill. Run it manually (/daily-retro 2026-01-31 propose)
or wire your own scheduler. No OS job is installed this way (plugins can't register cron).
Usage
/daily-retro # today, apply mode (or your config default)
/daily-retro 2026-01-31 # a specific day
/daily-retro 2026-01-31 propose # review-only, edits nothing
Outputs land in ~/.claude/retro/<date>/.
Modes
| Mode | What Step 3 does |
|---|
propose (safe default in wizard) | Writes 03-proposals.md with ranked, deduped recommendations + proposed diffs. Edits nothing. |
apply | Auto-creates/improves skills, edits the auto-section of ~/.claude/CLAUDE.md, bumps the changelog + registry. |
Start with propose, read a few nights of output, then switch to apply if you trust it.
How it keeps itself honest
