Analyze origin/main git history to generate weekly engineering retrospective reports.
npx skills add https://github.com/kadenn/kstack --skill retro-kadenn
Please help me install this Agent Skill. Skill: retro Source: https://github.com/kadenn/kstack/tree/main/retro Command: npx skills add https://github.com/kadenn/kstack --skill retro-kadenn
Analyzes origin/main git history to produce a comprehensive, actionable weekly engineering retrospective that surfaces patterns, wins, and improvement opportunities for the team.
Run the retro skill to generate a weekly engineering retrospective from your repo history.
High-intent search queries and answers about installing and using this skill.
To generate a weekly engineering retrospective from git history, analyze the origin/main branch log to compute commits, LOC, and PR size. This process parses git logs to produce a structured JSON snapshot and a narrative report surfacing team patterns and wins.
A git-based engineering retrospective includes metrics like per-author commits, insertions, deletions, test coverage proxies, PR size, session length distributions, and peak coding hours. These metrics identify focus areas and potential churn across multi-contributor projects.
Yes, you can analyze multi-contributor git logs to break down per-author focus areas. The retrospective computes individual contributions including commits, insertions, and deletions to identify specific development patterns and focus areas for each contributor.
Yes, the weekly retro analysis works with Greptile history. The implementation requires parsing git logs and optionally integrates Greptile history data alongside optional prior retros to deliver comparative analysis and structured JSON snapshots.
Compare current engineering metrics against previous retros by parsing optional prior retrospective data alongside current git logs. This comparison delivers a comprehensive narrative report highlighting improvement opportunities and tracking team productivity trends over weekly windows.
dyoshikawaAnalyze git differences and commit history between the current branch and origin main.
cswenorAnalyze weekly JSON snapshots to generate project health narratives.
jk278Analyze git repositories to summarize commit history and file changes.
yocxy2Analyze git commit history to generate engineering retrospectives.
