Weekly Review Generator

What this skill does

Pulls last week's calendar events, git commits across configured repos, and journal notes, then writes a markdown weekly review with: highlights, what shipped, where time went, lessons, and a primed list for next week.

Inputs

• calendar_ics: an iCal export of last week.
• repos: array of repo_dir paths to enumerate commits.
• notes_dir: directory holding daily/weekly notes.
• Optional goals_file: previous week's goals to track completion.

Steps

1. Bound the week: ISO week of now - 7 days. Pull events with start in the window.
2. Compute time-spent per category from event titles using a keyword map (1:1 -> coaching, interview -> hiring, [focus] -> deep-work).
3. For each repo, run git -C <repo> log --since='last Mon 00:00' --until='last Sun 23:59' --pretty='%h %s %an' --no-merges and capture authored-by-you commits.
4. Group commits by repo and by feature (parsing Conventional-Commit type prefix when present).
5. Read notes in notes_dir for the week. Extract bullets matching - [x] (done) and - [ ] (open).
6. Cross-reference with goals_file: which goals did [x] items satisfy?
7. Compose the review:
   • Highlights (3-5 bullets pulled from completed goals + notable commits).
   • Shipped (per-repo sub-section).
   • Time spent (a table by category with hours).
   • Lessons (extract from notes containing keywords "learned", "realized", "next time").
   • Next week (the open - [ ] items + uncompleted goals carried forward).
8. Save to <notes_dir>/weekly/<ISO-week>.md.

Output

<notes_dir>/weekly/<year>-W<week>.md with the five sections. Stdout prints completion rate (%done of last week's goals) and total commits.

Verification

Re-derive time-spent per category by running the calendar parse separately and comparing totals; mismatches usually mean a typo in the keyword map. Re-list commits with git log and confirm count matches the report. If notes_dir has fewer than 3 notes for the week, surface a note about underwriting; the review will be thin.

Edge cases

• No calendar export available: skip the time-spent table and surface "no calendar data".
• Repos where you're not the only author: filter by --author="<name>" consistently across repos.
• Notes split across many subdirs: walk recursively but skip archive folders by name (archive/, _old/).
• Holiday weeks: produce a short "low-volume" review rather than fabricate content.