Generates weekly engineering-retro metrics and narratives from git history.
npx skills add https://github.com/KSD-CO/IronCode --skill retro-ksd-co
Please help me install this Agent Skill. Skill: retro Source: https://github.com/KSD-CO/IronCode/tree/main/packages/ironcode/skills/retro Command: npx skills add https://github.com/KSD-CO/IronCode --skill retro-ksd-co
Engineering teams struggle to turn raw git history into actionable, time-bound insights that inform planning and process improvements.
Run the retro for the default 7-day window to generate metrics, a narrative, and a .context/retros JSON snapshot.
High-intent search queries and answers about installing and using this skill.
Engineering retrospectives from git history are generated by detecting the default branch and gathering commits within a retro window to aggregate metrics like LOC, test activity, and per-author contributions. This produces a JSON snapshot and a concise team-level narrative with actionable takeaways.
Team retrospective metrics from git commit history include commits, LOC, test activity, per-author contributions, hourly activity, hotspot files, commit types, and PR sizes. The analysis also parses Co-Authored-By trailers to accurately attribute pair programming work.
Tracking per-author contributions and session dynamics from git commits involves aggregating commits within a time window and parsing Co-Authored-By trailers. This identifies individual contribution levels, peak working hours, and session patterns to inform process improvements.
Comparing current engineering metrics with the previous week's retro is supported by generating a current JSON snapshot and narrative that includes comparisons to the prior retro when available. This highlights trends in commits, LOC, and test activity over time.
A Ship of the Week highlight in a development team retrospective identifies the most impactful change within the analysis window and provides the rationale for its significance. It draws directly from aggregated git metrics to focus team attention on high-value deliverables.
No specific dependencies are required to run a git workflow retrospective. The process operates directly on git history to detect the default branch, gather commits, and aggregate metrics into a JSON snapshot and narrative without external tool dependencies.
g4rcezAnalyze git commit history to generate data-driven weekly retrospective reports.
henrique-simoesAnalyzes research projects and generates actionable retrospective reports with prioritized recommendations and guardrails for team adoption.
NoobyGainsEnforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.
ManzuetiAnalyze commit history, code quality metrics, and PR metrics for engineering retrospectives.
