gstack-openclaw-retro

Run the retro generator on a weekly window of git commit history to produce per-author metrics, code quality signals, and hotspots. It outputs focus scores, session patterns, and a stakeholder-ready narrative summarizing the team's engineering performance.

Yes, you can compare engineering metrics across weekly windows using the optional compare mode. This feature leverages history persistence to track team performance trends, per-author contributions, and code quality signals over time.

A code quality and team performance retro includes per-author metrics, focus scores, PR-size estimates, and session patterns. It also highlights contribution hotspots and time-window based data like commits, LOC, and tests to inform planning and growth.

Yes, the retrospective outputs a Telegram-ready narrative and weekly ship insights suitable for sharing with stakeholders. This format summarizes the team's engineering contributions, focus scores, and growth opportunities in a readable summary.

To analyze per-author contributions and identify code hotspots, you need access to your team's weekly git commit history. The tool processes this commit data to highlight contribution hotspots, session patterns, and growth opportunities for engineers.

Use an automated engineering retro when you need to assess weekly team performance metrics and session patterns across multiple authors. It complements manual code reviews by providing quantitative focus scores and PR-size estimates to inform planning.