gstack-openclaw-retro

To generate a weekly engineering retrospective from git commit history, you run the 'gstack-openclaw-retro weekly' command. It analyzes commit data, evaluates code quality metrics, and summarizes team member contributions for your review.

A comprehensive team retrospective analysis requires engineering metrics like commit frequency, code quality checks, and individual contributor recognition. This skill parses git history to track these performance trends and highlight areas for team growth.

Yes, you can track team contributions and code quality using git history analysis. The skill reviews commit changes to evaluate code quality metrics and recognizes individual contributor efforts, highlighting both praise and areas for growth.

Yes, you need git access for commit analysis and team insights generation. The skill requires direct access to your repository data to parse commit history, evaluate code quality metrics, and calculate engineering productivity for the retrospective.

Automating engineering productivity tracking for weekly reviews is best achieved by systematically analyzing commit history and code quality metrics. This skill performs detailed code evaluations and presents team insights to monitor development workflow trends automatically.

You should use commit analysis for retrospective analysis when you need objective engineering metrics and trend tracking over time. It provides data-driven insights into code quality and individual contributions that manual team reviews might easily overlook.