Generate weekly engineering retrospectives from git logs, tests, and PR activity.
npx skills add https://github.com/rkumar261/studio-cast --skill retro-rkumar261
Please help me install this Agent Skill. Skill: retro Source: https://github.com/rkumar261/studio-cast/tree/main/.claude/skills/gstack/retro Command: npx skills add https://github.com/rkumar261/studio-cast --skill retro-rkumar261
Weekly engineering retrospectives that translate raw git history, commit activity, and code signals into a clear, actionable narrative for teams. It highlights praise, growth opportunities, and patterns that influence future delivery.
Run the retro skill with the desired window to generate a comprehensive weekly engineering retrospective summary.
High-intent search queries and answers about installing and using this skill.
To generate a weekly engineering retrospective, you can analyze commit histories, test stats, and PR activity over a default 7-day window to produce a structured narrative with per-author praise and growth opportunities.
Yes, you can analyze code quality metrics for individual team members by evaluating commit activity, lines of code, test health signals, and hotspot files to generate targeted per-person praise and growth opportunities.
The best way to compare engineering team activity across time periods is using a compare mode alongside configurable time windows like 24h, 14d, or 30d to assess changes in commit patterns and hotspot analysis over time.
Yes, the retrospective analysis works with backlog files by automatically detecting and incorporating backlog signals from TODOS.md when available, integrating this status into the final team-pace retrospective narrative.
To identify code hotspot files affecting team delivery, you analyze git logs and test health signals to pinpoint highly active files, generating actionable focus area signals and historical context for the engineering team.
fghaffarGenerate weekly engineering retrospective reports from Git commit history and metrics.
shihwesleyAnalyze Git history to generate weekly engineering retrospectives with per-author metrics.
howdeployAggregate type checker, linter, test, and dead code results into a 0-10 health score.
ComputerConnectionAnalyze weekly git activity to generate team-aware retrospectives with per-author metrics.
