What problem does it solve?
Provide objective, data-driven retrospectives by extracting measurable git metrics so teams avoid subjective guesswork and base sprint reviews on verifiable activity.
Core Features & Use Cases
- Automated Git Metrics: Collect commits, LOC added/removed, net LOC, file hotspots, churn, commit type distribution, active days, and per-author breakdowns.
- Health Indicators & Comparisons: Compute derived metrics (commit frequency, churn rate, test-to-code ratio, active-day ratio) and optionally compare to a preceding period.
- Plan and Issue Checks: Scan plans/ for checkbox progress and optionally use gh to count closed issues; export structured reports as Markdown or self-contained HTML.
- Use Cases: Run after a sprint, for weekly check-ins, or for ad-hoc reviews to identify hotspots, test coverage trends, and plan completion rates with concrete recommendations.
Quick Start
Run ck:retro with a timeframe (e.g., 7d, 1m, or YYYY-MM-DD:YYYY-MM-DD) and optional flags like --compare or --team to generate a retrospective report from the repository git history.