weekly-review

To summarize git commit history into a weekly recap, the tool extracts authored non-merge commits from the last 7-10 days, categorizes them into bug fixes, tech debt, and net-new work, and generates 2-5 grouped bullet points for status updates.

Classifying recent commits into bugfix, tech debt, and net-new work involves analyzing authored commit diffs on the primary branch to estimate work categories, producing a concise paragraph for engineering planning and retrospectives.

Yes, you can generate a weekly release notes summary by extracting authored commits from the primary branch over the past 7-10 days, filtering out merge commits, and grounding the recap strictly in the actual commit history and meaningful diffs.

Yes, the weekly review process explicitly excludes merge commits when generating a status update, ensuring the synthesis focuses strictly on authored, non-merge commits and meaningful diffs from the primary branch.

The commit history recap produces 2-5 bullet points for your retrospective, grouping meaningful diffs from the past 7-10 days of activity into concise change categories.

Yes, you need a configured git user identity because the weekly synthesis extracts commits specifically authored by that user identity from the primary branch to build the recap.