Analyze Git history to compute commits, insertions, deletions, and per-author metrics.
npx skills add https://github.com/onlypfachi/chief --skill retro-onlypfachi
Please help me install this Agent Skill. Skill: retro Source: https://github.com/onlypfachi/chief/tree/main/retro Command: npx skills add https://github.com/onlypfachi/chief --skill retro-onlypfachi
Weekly retrospectives are time-consuming and hard to extract useful patterns from raw git data. This Skill automates analysis of commit history, contributor activity, code quality signals, and team patterns to deliver a clear, narrative-focused engineering retrospective.
Run the retro for the default 7-day window to get the narrative, metrics, and team insights.
High-intent search queries and answers about installing and using this skill.
Generating an engineering retrospective from git history involves analyzing commits, insertions, deletions, and per-author metrics to assess team dynamics. It produces a narrative report with an executive summary, highlighting focus hours and suggesting concrete improvements for leadership reviews.
Weekly developer retrospectives should track commits, insertions, deletions, and per-author contributions to assess team dynamics. Evaluating these metrics highlights focus hours, session patterns, top contributors, test health, and potential ship-of-the-week items for actionable insights.
Yes, you can analyze individual contributor performance using git commit data by computing per-author metrics. This analysis highlights individual focus hours, session patterns, top contributors, and specific strengths, generating per-member praise and identifying concrete growth opportunities.
Identifying focus hours and session patterns from commit history requires analyzing timestamped git activity to map contributor workflows. This reveals peak productivity windows and coding session lengths, helping assess team dynamics, highlight top contributors, and suggest concrete improvements.
This retrospective tool works by analyzing standard git history within a configurable window, requiring no specific external dependencies. It processes native git data to compute commit metrics and generate narrative reports, making it compatible with standard repository workflows for leadership reviews.
CarbeneAIGenerate weekly engineering retrospectives from git logs and analytics files.
VertaKhanAggregate commit history and code quality metrics into weekly engineering retrospectives.
SpillwaveSolutionsCollect GitHub PR data and generate structured review files with two-stage approval.
huichenParse Git history and commit metadata to summarize engineering activity.
