Generate weekly engineering retrospectives from git commit history and code-quality signals.
npx skills add https://github.com/jerrywu001/jerrywu001 --skill retro-jerrywu001
Please help me install this Agent Skill. Skill: retro Source: https://github.com/jerrywu001/jerrywu001/tree/main/.claude/skills/retro Command: npx skills add https://github.com/jerrywu001/jerrywu001 --skill retro-jerrywu001
It eliminates the guesswork of what the team shipped this week and how work quality and effort patterns changed, by turning your git activity into a structured, time-aware engineering retrospective.
Ask for a weekly engineering retrospective by typing: /retro 14d
High-intent search queries and answers about installing and using this skill.
Engineering retrospectives analyze git commit history within a chosen time window to evaluate contributor activity, test coverage signals, and work patterns. They parse commit logs to produce structured snapshots of team contributions and code quality metrics for sprint reflection.
Analyzing commit history identifies team contributions by detecting session distributions via commit gaps and tracking per-person activity. It highlights peak hours, individual praise, and growth areas alongside code quality metrics for multi-contributor teams.
Tracking code quality metrics involves parsing git diffs to calculate test versus production file changes, identify hotspot files, and measure churn rates. This approach captures commit-type mixes and test coverage signals within a specific time window.
The weekly retrospective supports multi-contributor teams by parsing individual commit activity and session distribution. It integrates optional backlog telemetry hooks and greptile insights when available to enrich the engineering retrospective.
Run a sprint reflection by specifying a date range to analyze commit history. The system parses commit gaps to identify work sessions, calculates churn metrics, and saves a structured snapshot for tracking engineering trends across the sprint.
Without optional telemetry or greptile hooks, the retrospective relies solely on parsing git logs for commit and diff analysis. It still calculates code quality metrics and session distribution but lacks enriched backlog context for deeper engineering insights.
BerryKuipersExtract development events from git commits into ai_memory/events.jsonl.
anilveersingh1308Generate weekly engineering retrospectives from git commit history and test signals.
supertyrelleAnalyze git state and workflow signals to recommend prioritized next actions.
shogo-labsAnalyze commit activity, PR cycle times, and code churn for engineering health.
