weekly-review

To summarize git commits for a weekly status update, this skill collects authored commits from the last 7-10 days on the primary branch, excludes merges, and generates a concise executive recap with 2-5 bullets and a classification paragraph.

Generating an executive recap of weekly development activity is best done by grouping a week's meaningful commit changes into concise bullets and adding a brief classification paragraph covering likely bug fixes, tech debt, and net-new functionality.

Yes, the weekly commit recap works across multi-repo git contexts as needed. It applies to typical software projects with a primary branch and 7-10 days of available commit history, excluding merge commits from the summary.

To classify bug fixes and tech debt from recent git history, this skill analyzes your weekly commits and generates a brief classification paragraph distinguishing likely bug fixes, likely tech debt, and likely net-new functionality alongside the recap bullets.

The weekly commit recap prompts you to set a git email as a guardrail because it determines the current git user email from your repository config to accurately filter and collect only your authored commits from the 7-10 day window.