Analyze git commit history to generate weekly engineering retrospective reports.
npx skills add https://github.com/kk20300113-png/my-claude-skills --skill retro-kk20300113-png
Please help me install this Agent Skill. Skill: retro Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/retro Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill retro-kk20300113-png
Manual weekly engineering retrospectives are time-consuming, often miss key work patterns and individual contributions, and fail to track progress across sprints, leaving teams without actionable insights to improve their workflow.
Use the retro skill to run a weekly engineering retrospective for your team's current sprint.
High-intent search queries and answers about installing and using this skill.
Automate engineering sprint retrospectives by parsing git commit history to identify shipped work, code quality trends, and work patterns without manual log review. This process generates actionable retro reports in minutes instead of hours.
Track individual team contributions automatically using team-aware contribution breakdown logic. This highlights per-person contributions with specific praise and growth areas, making weekly code reviews fair and constructive.
Monitor long-term engineering productivity trends by utilizing persistent local storage for historical retro data. This approach spots long-term productivity patterns and measures workflow improvement over time across multiple sprints.
Automated retrospective analysis requires access to git repositories to parse commit history. It also requires persistent local storage for historical data and team-aware contribution breakdown logic to function correctly.
Automated commit analysis identifies bottlenecks and code quality metrics by parsing git commit history and work patterns. It applies this analysis to sprint-end team reviews to highlight where bottlenecks occurred and what to celebrate.
Avoid automated git commit analysis for team performance tracking if you lack access to git repositories or cannot provide persistent local storage for historical data, as these are strict requirements for generating accurate retrospective reports.
cegit27Analyze git commit history to generate weekly retrospective reports.
KrismithReddy12Analyze engineering commit history and project timeline data to generate automated retrospective reports.
joyce820309Analyze commit history and code quality for weekly engineering retrospectives.
fghaffarGenerate weekly engineering retrospective reports from Git commit history and metrics.
