gstack-openclaw-retro

To generate a weekly engineering retrospective from Git commit history, this Skill parses contributor activity and code-quality signals to produce a data-backed narrative with per-author praise and growth opportunities. It computes engineering metrics over a configurable time window.

Yes, you can track engineering metrics and code quality trends across multiple windows. The retrospective engine maintains persistent history, allowing teams to monitor contributor performance and code quality progression over time rather than just isolated weekly snapshots.

The best way to summarize what shipped this week is to analyze Git commit history for contributor activity and code-quality signals. This Skill generates a structured, team-aware narrative detailing per-author contributions and growth opportunities for post-ship reviews.

No, the retrospective engine requires no external dependencies or components to function. It independently parses Git commit data and computes engineering metrics to deliver the structured retrospective narrative without needing additional software setup.

Code quality insights factor into automated engineering retrospectives by analyzing Git commit history signals alongside contributor activity. The Skill uses these signals to identify code quality trends and generate specific growth opportunities for individual authors within the team narrative.