tkm:run-retro

Generate a sprint retrospective report from git history by analyzing commit frequency, code churn, and issue completion to produce structured markdown or HTML reports. This Skill automates the data collection to provide metrics and recommendations directly from your repository.

Git metrics analyzed for team performance and code quality include commit frequency, lines of code, code churn, and hotspots. These metrics derive health indicators that help identify areas needing attention during your sprint retrospective.

You need GitHub API access to track issue completion for retrospective reports if you want automated issue tracking. Git metrics analysis itself requires only the git client, but GitHub CLI access enables comprehensive issue completion metrics.

You can export retrospective reports as markdown or HTML with visualizations and recommendations. The Skill generates these structured report formats automatically after analyzing your repository's git history and computing health indicators.

This retrospective tool works with plain git repositories without GitHub for core git metric analysis like commit frequency and code churn. GitHub API access is optional and specifically needed only for tracking issue completion metrics.

Use git-based metrics instead of manual data collection for sprint retrospectives to reduce human error and save time. Automating analysis of commits, code churn, and hotspots provides objective health indicators and structured recommendations instantly.