Generate engineering retrospective reports from git history with Markdown or HTML output.
npx skills add https://github.com/jangtrinh/demo-Lam --skill ck-retro-jangtrinh
Please help me install this Agent Skill. Skill: ck:retro Source: https://github.com/jangtrinh/demo-Lam/tree/main/.claude/skills/retro Command: npx skills add https://github.com/jangtrinh/demo-Lam --skill ck-retro-jangtrinh
This Skill eliminates opinion-based retrospectives by collecting objective git metrics for a given period and turning them into a structured, evidence-backed report.
Run ck:retro for the last 7 days, optionally break down results by author, and output the report in Markdown.
High-intent search queries and answers about installing and using this skill.
To generate an engineering retrospective report from git history, this Skill collects commit cadence, active days, and LOC metrics for a specified timeframe, producing structured Markdown or self-contained HTML output. It applies deterministic date-range resolution to compute derived indicators for sprint or weekly cycles.
Git metrics for a data-driven sprint retrospective include commit cadence, active days, LOC added, removed, and net changes. The Skill also computes churn rate, commit type distribution, top file hotspots, and a test-to-code ratio proxy to identify code health and risk areas.
Yes, you can break down git churn analysis by author for a specific period. The Skill supports per-author breakdowns and period comparison, allowing you to evaluate individual contributions and velocity trends across sprint, weekly, or ad-hoc review cycles.
The retrospective report does not require external issue tracking tools, relying strictly on git-based metric collection with no invented values. It optionally scans a plans directory for checkbox progress and includes closed GitHub issue context if the GitHub CLI is available.
The best way to track code health and risk hotspots from git activity is by computing churn rate, commit type distribution, and top file hotspots. This Skill calculates these derived indicators alongside a test-to-code ratio proxy to highlight problematic areas objectively.
khapn-2933Generate sprint retrospective reports from git repository history.
mcauduro0Analyze sprint data with Monte Carlo simulations to forecast velocity and team health.
tranvietanh0Analyze git metrics and generate sprint retrospective reports.
a29paulGenerate weekly engineering retrospectives from git commit history and code quality metrics.
