Analyze git history to summarize engineering activity and code quality trends.
npx skills add https://github.com/curielmc/beat-SPY --skill retro-curielmc
Please help me install this Agent Skill. Skill: retro Source: https://github.com/curielmc/beat-SPY/tree/main/.claude/skills/gstack/retro Command: npx skills add https://github.com/curielmc/beat-SPY --skill retro-curielmc
The Retro Skill helps engineering teams capture a clear, data-driven weekly reflection by analyzing commit history, work patterns, and code quality metrics, with a persistent history and per-person praise and growth suggestions.
Run the /retro command to generate the weekly retrospective from the last 7 days.
High-intent search queries and answers about installing and using this skill.
A git retrospective analyzes recent commits to surface team highlights, work patterns, and code quality trends. Run the /retro command to summarize engineering activity from the last 7 days, producing a structured narrative and improvement plan.
A team-aware retrospective analyzes git commit history to highlight individual and team-wide engineering contributions. It tracks work patterns, test signals, and code quality trends over time, providing per-person praise and growth suggestions alongside a structured improvement plan.
Yes, you can analyze multiple repositories using Global Retrospective mode. This cross-repo analysis aggregates commits, authors, and backlog indicators across projects, providing a unified narrative and improvement plan for broader engineering teams.
Engineering metrics in a git retrospective include commit activity, author contributions, test signals, and backlog indicators. These metrics are extracted from git history and greptile data to identify code quality trends and team work patterns over time.
The retro analysis works without greptile history or TODO data, but utilizes them when available to enhance the retrospective. Core functionality relies on git commit history to analyze authors, test signals, and code quality trends for the structured narrative.
Track engineering trends over time by running weekly retrospectives that persist historical data. This captures commit activity, code quality metrics, and team contributions, enabling trend analysis and providing proactive rhythms and growth suggestions for sprint-end reviews.
snewhouseConvert git commit history into weekly engineering retrospective metrics.
richardnguyen0715Guide teams through structured retrospectives and document action items.
joyce820309Analyze commit history and code quality for weekly engineering retrospectives.
smarmen86Generates engineering retrospectives from git commit history and timeline events.
