Analyze git history to generate engineering retrospectives with velocity and hotspot metrics.
npx skills add https://github.com/shenxingy/Clade --skill retro-shenxingy
Please help me install this Agent Skill. Skill: retro Source: https://github.com/shenxingy/Clade/tree/main/configs/skills/retro Command: npx skills add https://github.com/shenxingy/Clade --skill retro-shenxingy
Retro skill turns git history into a clear, week-ready engineering retrospective so you can quickly understand development velocity, commit patterns, and hotspots without manual analysis.
Ask the AI for a weekly report by saying: "Run /retro 7d to generate a retrospective from my repository’s git history for the last 7 days."
High-intent search queries and answers about installing and using this skill.
To generate an engineering retrospective from git history, use commit analytics to quantify development velocity, detect work sessions from commit timing, and identify churn hotspots. This produces a data-driven report for week-over-week team reviews.
Commit analytics for development velocity measurement is the process of computing commit volume, lines added or removed, and active days from a repository. It reveals team work patterns and coding trends for a specified time window.
To detect churn hotspots in a git repository, analyze commit history to identify the most frequently changed files within a chosen period. This highlights areas of high code volatility and potential maintenance risk.
Yes, you can compare week-over-week development patterns using git logs by analyzing commit volume and work session timing across equivalent time windows. This comparison highlights shifts in development velocity and commit-type mix.
To identify work sessions from git commit timing, analyze the time gaps between sequential commits. Detecting these clusters reveals hourly distribution patterns and uninterrupted coding periods for retrospective reporting.
No, you do not need external dependencies to analyze commit patterns. The retrospective generation operates independently by directly parsing standard git history, computing metrics, and deriving work sessions without additional tools.
KrismithReddy12Analyze git commit history to generate engineering retrospectives and team performance metrics.
HouseofmvpsAnalyze git repository history to generate structured sprint retrospective reports.
tranvietanh0Analyze git metrics and generate sprint retrospective reports.
ByronWilliamsCPAComputes git commit analytics for development retrospective reports.
