gstack-openclaw-retro

Generate a weekly engineering retrospective by analyzing git commit history to automatically calculate commit counts, LOC changes, PR counts, test ratios, and session patterns. This replaces manual data gathering with actionable insights for sprint reviews.

Automated git analysis for sprint reviews includes commit counts, lines of code changes, PR counts, test ratios, and session detection. It identifies per-author wins, flags growth opportunities, and saves snapshots to track week-over-week team velocity trends.

Track individual contributor performance and code churn by applying per-author breakdowns to git history. The analysis highlights specific commit examples for team wins and provides data-backed growth opportunities without manual review.

You need access to a git repository with existing commit history to run an engineering retrospective. The analysis supports configurable time windows, allowing you to target specific weeks or custom date ranges for your sprint review data.

Week-over-week trend monitoring works by saving persistent retro snapshots from your git history. These stored snapshots allow direct comparison of team velocity, code quality metrics, and engineering habits across consecutive weeks.

Automate engineering retrospective preparation by pulling actionable insights directly from git commit history instead of relying on memory or scattered notes. This instantly generates a full report covering team bottlenecks, wins, and actionable improvements.