Aggregate git history into team-aware engineering retrospectives with per-author insights.
npx skills add https://github.com/AndrewLi0420/BMW --skill retro-andrewli0420
Please help me install this Agent Skill. Skill: retro Source: https://github.com/AndrewLi0420/BMW/tree/main/.claude/skills/gstack/retro Command: npx skills add https://github.com/AndrewLi0420/BMW --skill retro-andrewli0420
Weekly engineering retrospectives are time-consuming and error-prone when done manually. This Skill analyzes commit history, work patterns, and code quality metrics to produce a consistent, team-aware retrospective with persistent history and per-person insights.
Run the retro command to generate a report for the default 7-day window.
High-intent search queries and answers about installing and using this skill.
To generate an engineering retrospective from git history, run a command that aggregates commits, insertions, deletions, and test indicators to produce a team-aware report with per-author insights. The default window analyzes the past 7 days of activity.
A code-quality retrospective report includes metrics such as commit counts, code insertions, deletions, test indicators, and session patterns. It surfaces team-wide trends while providing per-author praise and growth opportunities for focused improvements.
You can compare engineering team performance over time using a dedicated compare mode. This feature supports configurable time windows like 24 hours, 7 days, or 14 days, allowing you to track progress and surface trends across retrospective periods.
The retrospective analysis operates without external dependencies, aggregating git history natively. It optionally integrates greptile and backlog data when available, with built-in validations and clear edge-case handling to ensure accurate reporting.
Customize the time range for a git retrospective by appending a duration parameter to the command, such as 24h, 14d, or 30d. The system defaults to a 7-day window if no specific time configuration is provided.
The best way to run a data-driven weekly retrospective is to analyze commit history and work patterns automatically, producing consistent per-person insights. This eliminates manual effort and errors while enabling productive 1:1s and focused improvements.
ekrishguptaAnalyze commit history and code quality metrics to generate engineering retrospectives.
ligianehuaAnalyze git commit history to generate a team-aware weekly retrospective.
xuithoiGenerates weekly engineering retrospectives from Git commit history and code metrics.
algorithmbasicsAnalyze git history to generate weekly engineering retrospectives with per-author insights.
