retro

Generate a weekly engineering retro by analyzing Git commit history to surface per-author contributions, code quality metrics, and team dynamics for the selected time window. The tool aggregates commits, insertions, deletions, and test data into a narrative interpretation and structured data snapshot.

A Git-based team performance retrospective includes per-author contributions, test health, hotspot analysis, and weekly trends. It aggregates commit insertions, deletions, test data, and session patterns to produce a structured data snapshot suitable for historical comparison.

Yes, you can compare engineering metrics and trends across different time windows using the optional compare mode. This allows you to analyze historical data snapshots generated from Git history to identify team performance trends and support future planning.

The engineering retro analysis supports individual reflections by providing per-person praise and growth notes for each contributor. It surfaces focus scores and ship-of-the-week analysis alongside team dynamics to identify personal growth opportunities.

You need access to your project's Git history to run a code quality and team dynamics retrospective. The analysis automatically aggregates commit data, test health, hotspots, and session patterns within the selected time window to generate a comprehensive narrative interpretation.

Use an automated Git retrospective for weekly reviews and team-wide trend analysis rather than manual code reviews. It surfaces per-author contributions, backlog checks, and work patterns efficiently, producing a structured data snapshot suitable for historical comparison and future planning.