Analyze commit history and work patterns to produce weekly retro summaries.
npx skills add https://github.com/LaPaGaYo/nexus --skill retro-lapagayo
Please help me install this Agent Skill. Skill: retro Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/support/retro Command: npx skills add https://github.com/LaPaGaYo/nexus --skill retro-lapagayo
Weekly retrospectives that capture commit history, work patterns, and code quality trends to drive continuous improvement.
Run a weekly retro to summarize recent work, surface insights, and generate actionable improvement items.
High-intent search queries and answers about installing and using this skill.
To generate a weekly retro, you analyze commit history and code quality metrics to surface work patterns, per-person contributions, and growth areas. This process requires persistent history and source data integration to output actionable summaries.
Sprint trend analysis tracks work patterns and code quality metrics across multiple sprints. It helps team feedback by surfacing persistent bottlenecks and growth areas, enabling continuous improvement and targeted coaching.
Yes, you can break down code quality and delivery patterns by individual team member. The analysis highlights specific contributions and identifies distinct growth areas for coaching and continuous improvement.
Yes, persistent history integration is required. Analyzing commit patterns and generating trend insights across sprints depends on accessing continuous source data to produce accurate and actionable summaries.
Using commit history for weekly retrospectives is limited by its focus on delivery patterns and code quality metrics. It may not capture external blockers or non-code contributions, requiring integration with broader source data for full context.
rahmanayonAnalyze commit history and contributor activity to produce structured weekly retros.
89jobrienStructure Agile standups, retrospectives, and sprint tracking with action items.
hilaryosborneFacilitate structured team retrospectives to identify delivery impediments and generate action items.
zzxtbetaAnalyze commit history and code quality metrics into weekly engineering retrospectives.
