Analyze commit history and generate per-contributor retro reports.
npx skills add https://github.com/txema-puch/drone-ai-saturdays --skill retro-txema-puch
Please help me install this Agent Skill. Skill: retro Source: https://github.com/txema-puch/drone-ai-saturdays/tree/main/.claude/skills/gstack/retro Command: npx skills add https://github.com/txema-puch/drone-ai-saturdays --skill retro-txema-puch
Weekly retrospectives help engineering teams systematically reflect on recent work, celebrate what went well, and identify concrete improvements to apply in the next sprint, improving velocity, code quality, and collaboration.
Run a retro for the current window to generate a team-focused summary and improvement plan.
High-intent search queries and answers about installing and using this skill.
Run an engineering retrospective by analyzing your git commit history to generate per-contributor praise, growth opportunities, and actionable insights for improving future sprints. The skill computes metrics like LOC, commits, and test coverage proxies to produce a structured team-focused report.
A weekly engineering retrospective systematically reflects on recent work to celebrate successes and identify concrete improvements for the next sprint. Analyzing team contributions and code quality metrics helps improve velocity, collaboration, and overall ship quality.
Yes, the retrospective handles multiple contributors by breaking down individual contributions and computing basic metrics such as LOC, commits, and test coverage proxies. It generates per-contributor praise and growth opportunities within a single structured report.
Track engineering growth across sprint windows by using the persistent history feature, which stores retro snapshots and trend data for comparison over time. This allows you to compare team praise and improvement areas across different weeks.
Yes, the retrospective skill surfaces concrete next steps and focus areas for the upcoming sprint based on the analysis of code quality metrics and commit history. It produces an improvement plan with clear emphasis on ship quality and team focus.
The best way to generate team praise from recent git contributions is to analyze the commit history for the selected retro window and compute per-contributor metrics. This approach automatically surfaces individual achievements and growth opportunities for the entire engineering team.
esopianAnalyze git commit history and code metrics to generate team retrospectives.
binfen1Analyze commit history and code quality metrics to generate weekly engineering retrospectives.
mostafasudoGenerate weekly engineering retrospective reports from git commit history.
shekerkammaAnalyze git commit history and code quality metrics to generate weekly engineering retrospective reports.
