Analyze commit history and code quality metrics to generate retrospective reports.
npx skills add https://github.com/benrapport/Vote-Better --skill retro-benrapport
Please help me install this Agent Skill. Skill: retro Source: https://github.com/benrapport/Vote-Better/tree/main/.claude/skills/gstack/retro Command: npx skills add https://github.com/benrapport/Vote-Better --skill retro-benrapport
Weekly retros analyze commit history, team work patterns, and code quality metrics to surface actionable insights and celebrate progress.
Run the /retro command to generate a weekly engineering retrospective for your repository.
High-intent search queries and answers about installing and using this skill.
You can analyze team work patterns by running the /retro command, which parses commit history and code quality metrics to surface actionable insights. It identifies per-person contributions and highlights both progress to celebrate and areas for growth.
Yes, you can track engineering performance trends across multiple sprint cycles. The retrospective process maintains persistent history, allowing you to compare code quality metrics and work patterns over time to identify long-term team performance trends.
Generating a code quality retrospective does not strictly require remote repository access. The analysis can be performed using either a local or remote git history, provided the tool has access to the repository data needed to evaluate commit history and work patterns.
The best way to analyze per-person contributions in a software engineering team is by evaluating commit history and code quality metrics. This approach surfaces actionable insights by identifying individual praise areas and growth suggestions based on actual repository data.
To propose actionable items at the end of a sprint, analyze your team's commit history and code quality metrics. This process generates proactive end-of-week suggestions and a structured report to guide upcoming work based on identified performance trends.
yocxy2Analyze git commit history to generate engineering retrospectives.
akillnessFacilitate structured sprint retrospectives with Start-Stop-Continue, Mad-Sad-Glad, or 4Ls templates.
ManzuetiAnalyze commit history, code quality metrics, and PR metrics for engineering retrospectives.
fghaffarGenerate weekly engineering retrospective reports from Git commit history and metrics.
