← ClaudeAtlas

weekly-automation-reviewlisted

Use on a weekly (Monday) cadence, or when asked what repetitive work is worth automating, what to turn into a skill/hook/tool, or to review recent activity for automation opportunities. This is the skill the scheduled Monday remote agent invokes. Triggers on recurring-task review, "what should I automate", and end-of-week/start-of-week retrospectives.
mickzijdel/dev-hooks · ★ 0 · AI & Automation · score 70
Install: claude install-skill mickzijdel/dev-hooks
# Weekly Automation Review Once a week, look back at recent work, spot the tasks you did by hand more than once, and recommend **1–2** of them to automate into a skill, hook, or tool. The discipline is to automate deliberately on a cadence instead of only when something annoys you in the moment. ## What it reviews - **Recent git activity** — commits/branches in the working repo over the last 7 days (`git log --since='7 days ago' --stat`); what kinds of changes repeated? - **The off-topic backlog** — `plans/off-topic-improvements.md` if present; recurring themes there are automation candidates. - **Repetition signals** — the same multi-step manual workflow done more than once, the same class of fix, the same checklist run by hand. - **The previous report** — read the last file in `plans/automation-reviews/` so recommendations build on prior ones and you can note what actually got automated (self-improving loop). ## Procedure 1. Read the previous report (if any) and note which past suggestions shipped. 2. Gather the week's activity from the sources above. 3. Identify repeated workflows — favor ones that are **high-volume, well-defined, low blast-radius, and measurable**. 4. Pick the top **1–2** and, for each, specify: what it is, whether it's best as a **skill / hook / tool**, a rough effort estimate, and the first concrete step. 5. Write the dated report (below) and post a one-paragraph summary to the user. ## Output Write to `plans/automation-reviews/YYYY-MM-DD.md`: `