gstack-retro

To generate a weekly engineering retrospective, the Skill analyzes local git log history, pull requests, and code metrics over a selected period to summarize team contributions and trends. You simply type /retro to initiate the automated data collection and report generation.

Engineering retrospective analysis evaluates commit history and code churn to pinpoint code hotspots and collaboration trends. It processes git logs across repositories to detect highly active files and summarize team activity for continuous improvement strategies.

Yes, the tool operates across repositories by processing local git data and project metadata. It requires access to your local git environment to gather commit history, PR activity, and code metrics for cross-project team analytics.

Yes, you can measure team contribution and code quality by analyzing commit history and pull request activity. The Skill generates detailed summaries of individual contributions, code churn, and collaboration metrics to inform data-driven team improvements.

The best way to analyze pull request activity and code churn is using an automated retrospective tool that aggregates this data across repositories. This approach provides trend analysis and identifies hotspot files, turning raw project metrics into actionable team insights.