weekly-work-loglisted

Build and refresh the brycewatson.com "Weekly Work Log" report page (/report, archived under /log) for the last completed week. Discovers the week's work from session-end handoffs + git, distils it into honest public-voice items, re-derives and verifies every number, and (unattended, every Sunday night) opens a review PR. Never publishes unattended.
BryceEWatson/claude-global-skills · ★ 0 · AI & Automation · score 75

Install: claude install-skill BryceEWatson/claude-global-skills

# Weekly Work Log Builds and refreshes the **Weekly Work Log** at `brycewatson.com/report`: a per-project feed of the specific work Bryce did **last week**, each item with an honest status badge and an expandable evidence drawer, a git-derived commits/day chart for the week, and per-project archive pages. Each week's report is snapshotted; `brycewatson.com/log` is the index of all past weekly reports. Routes: `/report` (live, current week) · `/report/<project>` (per-project commit-history archive) · `/log` (index of weekly reports) · `/log/<week>` (an archived week). **Target project:** `%USERPROFILE%\Projects\brycewatson.com`. The page + build scripts live there; this skill is the reusable orchestrator + the weekly scheduler. ## The window: the last completed week The report always covers the most recently **completed Monday–Sunday week** (a week completes on Sunday). Run on a Sunday night, that is the week that just ended; run any other day, it is the previous full week. Discovery (handoffs + git), the chart, and the per-project metrics all use this same week. It is anchored on the calendar week, never a rolling window walking back from today. ## What runs where Everything runs LOCALLY (it reads `~/.claude` handoffs + the sibling repos under `%USERPROFILE%\Projects\`); GitHub Pages CI cannot. The committed JSON is what CI builds, exactly like `art.json`/`books.json`. - `<repo>/src/data/work-log.source.json` — AUTHORED, approval-gated content (the human gate). - `<re