Analyze commit history and work patterns to generate weekly engineering retrospectives.
npx skills add https://github.com/bajajvinamr/little-wins --skill retro-bajajvinamr
Please help me install this Agent Skill. Skill: retro Source: https://github.com/bajajvinamr/little-wins/tree/main/.claude/skills/gstack/retro Command: npx skills add https://github.com/bajajvinamr/little-wins --skill retro-bajajvinamr
Weekly engineering retrospectives are often shallow. This Skill analyzes commit history, work patterns, and code quality metrics to surface team-aware praise and growth areas, making retros more data-driven and actionable.
Ask Claude to run /retro to generate this week's engineering retrospective.
High-intent search queries and answers about installing and using this skill.
An engineering retro analyzes commit history and code quality metrics to surface per-person praise and growth areas. It makes retrospectives data-driven by tracking contributor activity, work patterns, and persistent trend history across software projects.
Run a weekly retrospective by triggering the /retro command to analyze commit history and code quality metrics. It produces team-aware insights, surfacing per-person praise and growth areas to generate actionable improvements for sprint rituals.
Yes, you can track code quality and contributor trends over multiple sprint cycles using persistent history. The retrospective process retains work pattern data across retros to identify long-term growth areas and surface consistent per-person praise.
Yes, the weekly retro workflow integrates with existing sprint rituals and the gstack workflow. It applies data collection, validation, and output formats directly to your software projects to seamlessly surface actionable improvement insights.
The best way to identify per-person growth areas is by analyzing commit history and work patterns. This data-driven retrospective approach surfaces individual contributor metrics and generates actionable insights for targeted sprint improvements.
imonmiAnalyze weekly commit history and code quality for team retrospectives.
BradliebsAnalyze commit history and work patterns to generate weekly engineering retrospectives.
OpenAnalystIncCoordinates team rituals and manages workflows through customizable, automated processes in Notion.
sadie100Analyze commit history, work patterns, and code quality metrics for weekly retrospectives.
