gstack-openclaw-retro

To generate a weekly engineering retrospective, you can run the Skill against your git repository to analyze commit metrics, LOC changes, and work session patterns. It automatically parses the default branch history to produce actionable team insights.

You can track developer productivity and shipping velocity across custom time windows ranging from 24 hours to 30 days. The Skill analyzes commit history to calculate shipping velocity and saves snapshots for trend comparison.

Yes, it requires access to a git repository with commit history on the default branch to perform team code quality analysis. It parses commit data, test ratios, and PR data to evaluate code quality metrics for the team.

Code quality metrics and individual contributor work patterns are calculated by parsing git commits, LOC changes, and test ratios. The Skill generates per-contributor leaderboards and identifies personalized growth opportunities based on actual commits.

The best way to compare week-over-week engineering progress is by persisting retrospective snapshots to a local memory directory. This allows the Skill to track trends in shipping velocity, test discipline, and focus metrics over time.

A limitation is that the analysis requires commit history on the default branch, meaning detached commits or unmerged branches are excluded. Retrospective snapshots are also stored locally, which restricts trend tracking to a single environment.