retro

You can automate weekly engineering retrospectives by prompting 'weekly retro' to analyze commit history, work patterns, and code quality signals. The skill reads repository data to compute per-person contributions, trends, and growth areas without manual synthesis.

A team-aware engineering retrospective includes per-person contributions, commit history trends, work patterns, and code quality metrics. These signals are tracked persistently to surface praise and growth areas for proactive team improvement.

Generating per-person contribution insights for a sprint requires reading repository commit history and code quality data. The skill processes these work patterns to break down individual contributions and highlight specific growth areas.

Yes, you need the gstack runtime to run engineering trend analysis. The skill requires this runtime alongside Bash, Read, Write, Glob, and AskUserQuestion tools to read repository data and compute metrics for actionable insights.

Yes, you can track code quality trends and engineering growth areas over time using persistent history tracking. The skill stores retrospective data across weekly sprints and project cycles to establish trend baselines for proactive improvement.

Using commit history for retrospective analysis is limited to quantifiable work patterns and code quality signals. It requires repository data access via Bash and Glob tools and cannot capture qualitative team dynamics outside of commit metadata.