Analyze commit history and code quality metrics to generate weekly retrospectives.
npx skills add https://github.com/xotong/claude-marketplace --skill retro-xotong
Please help me install this Agent Skill. Skill: retro Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/gstack/skills/retro Command: npx skills add https://github.com/xotong/claude-marketplace --skill retro-xotong
Weekly retrospectives for engineering teams are often tedious and disconnected from actionable outcomes. This skill analyzes commit history, work patterns, and code quality metrics to provide persistent history and trend tracking, helping teams reflect and improve.
Invoke the retro skill at sprint end to generate a weekly retrospective with prior contributions and trends.
High-intent search queries and answers about installing and using this skill.
Automate weekly retrospectives by analyzing commit history, work patterns, and code quality metrics to surface trends. The skill gathers inputs, persists historical data, and renders actionable per-person contribution breakdowns with praise and growth areas.
Git history trend analysis for team performance evaluates commit patterns and code quality metrics over time. It surfaces actionable trends, helping engineering teams reflect on work patterns and guide continuous process improvements at sprint or weekly cycle ends.
Yes, you can generate per-person contribution breakdowns from commit history. The analysis highlights individual praise and growth areas based on work patterns and code quality metrics, providing targeted feedback for each team member.
The best way to run a sprint-end retrospective is invoking an automated analysis of commit history and code quality metrics. This surfaces persistent trend tracking and actionable insights, guiding process improvements without manual data gathering.
Yes, the retrospective analysis requires a Bash-based execution environment. It utilizes Read, Write, Glob, and AskUserQuestion capabilities to gather inputs, persist historical retrospective data, and render the final actionable reports.
Automated retrospectives solve the problem of manual reviews being tedious and disconnected from actionable outcomes. By analyzing commit history and code quality metrics, they provide persistent trend tracking and per-person breakdowns to guide continuous improvement.
ericdahl-devAnalyze commit history, work patterns, and code quality metrics for weekly engineering retrospectives.
JeremiahEllingtonAnalyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.
ShmurdocAutomate weekly engineering retros from git commit history.
shekerkammaAnalyze git commit history and code quality metrics to generate weekly engineering retrospective reports.
