retro

Generate a weekly team retrospective by analyzing git logs, per-author statistics, and code-quality signals to produce a structured report with per-person praise and growth recommendations. Run /retro on your repository to automatically collect contribution metrics and output leadership-ready insights.

Yes, contribution metrics analysis applies to both single-repo workflows and multi-repo teams. The system aggregates per-author statistics across repositories to generate a unified team-aware retrospective, tracking historical trends and providing growth opportunities for the entire engineering team.

Code-quality signals are extracted from commit history and per-author statistics to identify growth opportunities. The retrospective analyzes contribution metrics and work patterns to generate proactive suggestions at sprint end, offering personalized praise and targeted recommendations for each team member.

Yes, the retrospective tool maintains persistent history and trend tracking across sprints. By analyzing commit history and contribution metrics over time, it generates structured reports that visualize team progress, per-author growth, and evolving code-quality signals for engineering leadership.

You need an automated team retrospective when weekly manual reviews become time-consuming and inconsistent. By analyzing commit history and code-quality signals automatically, the system ensures structured, data-driven per-author insights and proactive growth suggestions without requiring manual data collection.

Retro is suitable for both single-repo workflows and multi-repo teams. It analyzes commit history and contribution metrics across either environment, generating a team-aware weekly retrospective with per-author praise, growth recommendations, and historical trend tracking regardless of repository scale.