retro

Generate a weekly engineering retrospective by analyzing git commit history and coding activity on origin/main. The tool extracts commit data, converts times to Pacific time, and exports metrics like commits, LOC, and tests to a narrative report saved under .context/retros.

Yes, you can analyze individual developer contributions from repository activity. The retrospective generates per-author insights, identifies focus areas, and highlights growth opportunities for each team member based on their commit history.

The weekly retrospective analysis works specifically with repositories tracked on origin/main. It evaluates coding activity within defined time windows like 7, 14, or 30 days to produce trend analyses and per-author insights.

A git workflow analysis for engineering teams includes metrics such as commits, lines of code, tests, and coding sessions. It maintains persistent history to compare weekly performance shifts and identify team-wide work patterns.

Persistent history helps track engineering team performance by saving retrospective reports under .context/retros. This allows you to compare weeks, spot shifts in code quality trends, and plan mentorship based on historical data.

The best way to automate weekly analytics for coding activity is to run the retrospective tool on your repository. It automatically extracts git data, calculates engineering metrics, and produces a narrative report with team-wide patterns and individual insights.