Analyze git history and team activity to generate weekly engineering retrospectives.
npx skills add https://github.com/ibalasite/gstack --skill retro-ibalasite
Please help me install this Agent Skill. Skill: retro Source: https://github.com/ibalasite/gstack/tree/main/retro Command: npx skills add https://github.com/ibalasite/gstack --skill retro-ibalasite
Weekly engineering retrospectives that analyze commit history, work patterns, and code quality metrics with a team-aware perspective, delivering praise and growth guidance.
Run /retro to generate the current week's engineering retrospective.
High-intent search queries and answers about installing and using this skill.
Generating a weekly engineering retrospective from git history involves analyzing recent commits and team activity to identify patterns across contributors, hotspots, and code quality signals. The tool outputs per-author praise and growth areas.
An engineering retrospective tracks code quality metrics, commit history, and work patterns to reveal trends across sprints. It provides per-person contribution breakdowns and actionable feedback to guide team growth and planning.
Yes, you can run retrospectives for a single-team project over a specific week window. The analysis applies to single-team projects, processing local analytics and git data to produce concise, actionable feedback.
To get per-author praise and growth areas from recent commits, run a weekly engineering retrospective. It identifies patterns in recent commits and team activity, delivering concise, actionable feedback for each contributor.
Yes, there is an optional global retro mode for analyzing multiple contributors. It identifies patterns in recent commits and team activity to produce an actionable weekly engineering retrospective across contributors.
You should not use automated engineering retrospectives outside a single-team project context or a one-week window. The analysis is specifically scoped to recent commits and local analytics data over a weekly period.
24601Generate weekly or cross-project engineering retrospectives from git history and contributor activity.
andrew-t-jamesAnalyze the last 7 days of commits to generate a structured team retrospective.
xuithoiGenerates weekly engineering retrospectives from Git commit history and code metrics.
EhsaanArkAnalyzes git history and team metrics to generate weekly retrospective narratives with growth recommendations.
