retro

Generating a weekly retrospective from git history involves analyzing commit activity, work patterns, and code metrics across defined time windows to produce structured per-person insights and actionable growth items.

Git commit analysis for sprint reviews is the process of examining repository history to summarize shipping velocity, detect code hotspots, and generate highlight reels for team growth discussions and planning sessions.

Yes, you can analyze multiple repositories and branches for team insights. The skill performs per-author breakdowns and hotspot detection across various repos and branches to support comprehensive sprint planning.

Yes, the retrospective analysis works with remote git repositories. The skill requires access to either local or remote repositories to perform commit analytics and generate per-author contribution breakdowns.

To track engineering team growth over multiple sprints, the skill performs trend analysis on git history to identify improvement opportunities, highlight contributions, and generate actionable growth items for review sessions.

Limitations of automated git history retrospectives include dependence on commit data quality and access to local or remote repositories, meaning the analysis relies entirely on historical code activity rather than real-time team feedback.