weekly-report

# Weekly Report ## When to use Invoke this skill when the user asks for a status update, weekly digest, or "sprint summary" derived from repository activity. ## Steps 1. Collect commits and merged PRs since the start of the week (`git log --since`). 2. Group them by theme: Features, Fixes, Chores, Docs. 3. Note any incidents or blockers mentioned in issues. 4. Write 3–5 bullets a manager can skim, then a one-line headline. 5. Offer to post it to the team channel or save it to a file. ## Examples - "Write this week's progress report" - "Summarize what the team shipped since Monday" ## References Prefer impact ("shipped X") over activity ("committed Y"); link PRs so readers can dig in.