retro

To generate a weekly engineering retrospective from git commit history, you can run the /retro command. It analyzes the last 7 days of commit history, work patterns, and code quality metrics to produce a narrative and structured metrics snapshot.

An automated engineering retrospective analyzes git commit history, work patterns, and code quality metrics to summarize team performance. It provides per-person praise and growth opportunities, delivering a concise narrative plus a structured metrics snapshot for leadership review.

Yes, you can use this for team analysis because it breaks down per-person contributions. It evaluates individual commit history and work patterns to provide specific praise and growth opportunities for each contributor on the team.

The best way to track engineering work patterns and code quality metrics over time is using a team-focused weekly retrospective. It synthesizes git commit history with persistent history and trend tracking to generate consistent leadership reviews.

You should not use an automated engineering retrospective if your team lacks git commit history or code quality metrics for the last 7 days. The analysis requires evaluating these work patterns to generate per-person praise and growth opportunities.