Generate structured retrospective reports from git history and PR data.
npx skills add https://github.com/lucas-flatwhite/gstack-ko --skill retro-lucas-flatwhite
Please help me install this Agent Skill. Skill: retro Source: https://github.com/lucas-flatwhite/gstack-ko/tree/main/retro Command: npx skills add https://github.com/lucas-flatwhite/gstack-ko --skill retro-lucas-flatwhite
Regular retrospectives often lack structure and measurable signals. This Skill aggregates a defined window of engineering activity—commits, code quality signals, and contributor behavior—into a coherent narrative that guides improvement.
Invoke /retro in your repository to generate a weekly retrospective (default last 7 days) and view structured insights.
High-intent search queries and answers about installing and using this skill.
To generate engineering retrospectives from git history, invoke the tool in your repository to analyze commits, code quality signals, and contributor behavior over a defined time window, producing a structured narrative report with actionable next steps.
A repository retrospective includes engineering metrics such as per-person contributions, shipping velocity, commit patterns, PR sizes, test activity, and hotspot files to surface risks and opportunities for team coaching.
Yes, you can analyze cross-project engineering activity by applying the tool to a global view, allowing you to summarize patterns across multiple repositories over a custom time window instead of the default 7-day single repository scope.
Code quality signals factor into weekly team retrospectives by analyzing test activity and hotspot files alongside commit patterns, identifying specific risks and opportunities to highlight praise and growth areas for focused coaching.
The retrospective analysis does not strictly require external analytics data, as it consumes git history and PR data by default, but it can process optional analytics alongside test signals to enrich the structured retrospective report.
The default time window for summarizing engineering activity is 7 days, applying to repository history to generate a weekly retrospective with sections on focus, shipping velocity, and code quality signals.
fghaffarGenerate weekly engineering retrospective reports from Git commit history and metrics.
cegit27Analyze git commit history to generate weekly retrospective reports.
josephneumannAnalyze Git commit history to generate engineering retrospective reports.
snewhouseConvert git commit history into weekly engineering retrospective metrics.
