retro

Generate a weekly engineering retrospective by analyzing repository commit history to surface team contributions and code quality metrics. Run /retro to process the current project's git logs and produce per-author praise and growth insights for the default 7-day window.

A team-aware engineering retrospective analyzes commit history to track per-author praise, growth opportunities, team alignment, and session patterns. It parses git logs across fixed windows to surface code quality metrics and actionable outcomes for the whole team.

You can run cross-project global retrospectives across multiple repositories or a multi-repo workspace. The analysis compares periods and tracks trends globally, evaluating team alignment and engineering growth across your entire codebase rather than a single project.

You can analyze commit history using fixed time windows of 24 hours, 7 days, 14 days, or 30 days. The 7-day window is the default for weekly retrospectives, while shorter or longer windows support daily check-ins or extended sprint analysis.

The retrospective analysis provides proactive suggestions at the end of a work week or sprint to guide next steps and focus. These actionable outcomes are generated from commit patterns and code quality metrics to help the team learn and improve over time.

Commit history analysis for engineering growth relies on git data, capturing only coding activity and missing non-code contributions like design or planning. Retrospective insights are limited to per-author commit patterns and code quality metrics within the analyzed repositories.