gstack-openclaw-retro

Generate a weekly engineering retrospective by aggregating git commit history, per-person contributions, and code quality metrics. The Skill analyzes the last 7 days by default to produce a comprehensive team-aware narrative summary.

Yes, you can run a git metrics retrospective for custom time windows. The Skill supports 24h, 14d, and 30d windows in addition to the default 7-day period, with a compare option to measure metric changes against the previous period.

An engineering team retrospective identifies individual praise and growth opportunities by analyzing per-person contributions and code quality metrics. It synthesizes commit history into a team-aware summary highlighting specific patterns and areas for each contributor.

The best way to share engineering retrospective insights in Telegram is to use a Skill that summarizes findings in a narrative format. This Skill formats team-aware retrospective results, including per-contributor praise, specifically for sharing in team channels.

Yes, you can compare engineering activity metrics against the previous period automatically. The Skill includes a compare option that measures changes in commit history and code quality metrics relative to the immediately preceding time window.

No external dependencies are required to analyze code quality metrics for a sprint retrospective. The Skill operates independently to aggregate repository activity and per-person contributions without relying on additional external tools or components.