Analyze git commit history and code quality metrics to generate engineering retrospective reports.
npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill retro-shmurdoc
Please help me install this Agent Skill. Skill: retro Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-retro Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill retro-shmurdoc
Engineering teams lose context between sprints, struggle to recall what shipped, and miss patterns in individual contributions and code quality trends. Manual retrospectives are often biased, incomplete, and fail to track progress over time.
Use the retro skill to analyze this week's engineering contributions and generate a structured retrospective report with team metrics and individual highlights.
High-intent search queries and answers about installing and using this skill.
Generate a sprint retrospective from git commit history by analyzing work patterns and code quality metrics to produce structured reports with team praise and growth areas. It parses version control data to identify shipped features, bug fixes, and refactors automatically.
Track individual engineering contributions and code quality trends over time using persistent history data across sessions. It monitors commit frequency, PR sizes, and review turnaround to surface productivity trends and generate per-person contribution summaries.
Automated engineering retrospectives require git repository access and gstack tooling to parse version control history. These dependencies allow the system to analyze commit data and produce structured reports with team metrics and individual highlights.
Data-driven retrospectives improve upon manual sprint reviews by eliminating bias and tracking persistent trend data across sessions. They automatically parse git history to surface bottlenecks, monitor code quality, and measure improvement in velocity and collaboration over time.
Analyzing commit frequency for team analytics is limited to repositories with accessible git history and gstack tooling. It relies on version control data to monitor work patterns, meaning incomplete commit logs will affect the accuracy of the generated retrospective reports.
ibalasiteUpgrade gstack installations across global git, local git, and vendored scenarios.
tim-krauszGenerate team analytics retrospectives from notebooks, velocity, and reproducibility trends.
SoSoBurnerAnalyze git commit history and code quality metrics for engineering retrospectives.
shekerkammaAnalyze git commit history and code quality metrics to generate weekly engineering retrospective reports.
