Analyze git commit history and code quality metrics to generate engineering retrospectives.
npx skills add https://github.com/robertzengcn/aiFetchly --skill retro-robertzengcn
Please help me install this Agent Skill. Skill: retro Source: https://github.com/robertzengcn/aiFetchly/tree/main/.agents/skills/gstack/retro Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill retro-robertzengcn
Manually compiling weekly engineering retrospectives is time-consuming, often lacks historical trend context, and makes it hard to deliver fair, consistent per-person contribution feedback. This skill automates the entire process by pulling commit history, work patterns, and code quality metrics to deliver data-driven retros without manual data gathering.
Use the retro skill to generate a weekly engineering retrospective for the current sprint, including per-person contribution breakdowns and trend analysis from past retros.
High-intent search queries and answers about installing and using this skill.
Generate a weekly engineering retrospective by using this skill to analyze git commit history, work patterns, and code quality metrics. It compiles data-driven retro documentation without manual data gathering, saving hours of preparation time.
Automated sprint review analysis evaluates team contributions by pulling git commit data to identify shipped work and bottlenecks. This skill applies that mechanism to deliver consistent, data-driven retrospectives without manual compilation.
Yes, you can get per-person contribution breakdowns for your engineering team's retro. This skill generates per-person summaries highlighting individual strengths and growth areas to eliminate bias from manual recall during sprint reviews.
Track cross-sprint engineering trends by using this skill's persistent local storage to store retro history. It compares progress across sprints to help teams spot recurring issues and measure improvement over time.
Yes, this retrospective tool works for a 6-person engineering team running 2-week sprints. It automatically highlights key shipped features, identifies common blockers, and gives each team member actionable feedback.
The best way to automate code quality metrics reporting for sprint reviews is using this skill to pull git commit history and identify code quality trends. It cuts retro prep time from hours to minutes by integrating with stored project artifacts.
KrismithReddy12Analyze git commit history to generate engineering retrospectives and team performance metrics.
JeremiahEllingtonAnalyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.
garrytanGenerate engineering retrospective reports from git commit history and code quality metrics.
kk20300113-pngAnalyze git commit history to generate weekly engineering retrospective reports.
