weekly-work-log

Automate weekly work log collection, verification, and PR publication from git history.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/BryceEWatson/claude-global-skills --skill weekly-work-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-work-log
Source: https://github.com/BryceEWatson/claude-global-skills/tree/main/weekly-work-log
Command: npx skills add https://github.com/BryceEWatson/claude-global-skills --skill weekly-work-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Builds and refreshes the Weekly Work Log at /report: a per-project feed documenting last week's work, with an honest status badge, an expandable evidence drawer, a git-derived commits/day chart, and per-project archive pages. Each week's report is snapshotted; /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.

Core Features & Use Cases

  • Discover: scan session-end handoffs across allowlisted repos, extract tagged claims and citations, redact sensitive items.
  • Distill & Verify: convert digests into public-voice items, re-derive all dates/numbers from git, and verify each cited commit resolves.
  • Publish: on Sundays, automatically open a review PR with the refreshed data for human review.

Quick Start

Copy the weekly-work-log directory into your Claude skills folder and invoke the interactive weekly-work-log flow.

Frequently Asked Questions about weekly-work-log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate weekly work reporting from git history and session handoffs?

Automated weekly work reporting collects session-end handoffs and git commit history across allowlisted repos, verifies cited commits, redacts sensitive fields, and publishes a per-project work log to a review PR unattended.

Can I generate a weekly work log that automatically opens a pull request for review?

Yes, the weekly work log automation publishes refreshed per-project data with commit evidence and archive indexes, then automatically opens a review PR on Sundays for human review before deployment.

Does weekly work log automation verify that cited commits actually resolve in git?

Weekly work log automation re-derives all dates and numbers directly from git history and verifies that each cited commit resolves, ensuring deterministic data derivation and accurate evidence for reported items.

How are sensitive fields handled when publishing a public-facing weekly report?

Sensitive fields are redacted during the distillation phase, where session-end handoff digests are converted into public-voice items before being published to the live report and archived weekly.

What is the best way to reconcile session handoffs with git history for a multi-project report?

Multi-source reconciliation scans session-end handoffs across allowlisted repos, extracts tagged claims and citations, and cross-references them with git commit history to produce per-project items with verified evidence.

Do I need specific repos allowlisted to run automated weekly work log collection?

Yes, you must define allowlisted repositories for the automation to scan session-end handoffs and git history, ensuring the weekly report only aggregates data from approved project sources.