retro

You can generate a weekly retrospective from git commit history by prompting Claude to analyze your commits, work patterns, and code-quality metrics to produce a team-aware report highlighting per-person praise and growth areas.

A team-aware engineering retrospective summarizes commit history and code-quality metrics to surface team-wide insights, tracking long-term trends and highlighting strengths and growth areas for each contributor across repositories.

Yes, you can track code-quality metrics and sprint progress across multiple repositories by analyzing git history and optional telemetry to produce repeatable reports that track long-term trends and cross-contributor contributions.

You do not need telemetry data to run a sprint retrospective, as the tool requires access to git history to function, but optional telemetry can be added to enhance the code-quality metrics and work pattern insights.

The best way to automate sprint boundary retrospectives is to proactively prompt the analysis tool to summarize engineering activity and code quality at sprint boundaries, generating persistent historical reports for your team.

Yes, the weekly engineering reports are privacy-conscious when analyzing individual contributor data, as the tool is designed to produce repeatable reports that surface team insights while maintaining privacy standards.