Generate markdown or HTML sprint retrospective reports from git metrics.
npx skills add https://github.com/Thanh-apero/apero-kit-cli --skill ck-retro-thanh-apero
Please help me install this Agent Skill. Skill: ck:retro Source: https://github.com/Thanh-apero/apero-kit-cli/tree/main/.claude/skills/retro Command: npx skills add https://github.com/Thanh-apero/apero-kit-cli --skill ck-retro-thanh-apero
This Skill automates the collection and analysis of git metrics to generate a structured report for sprint retrospectives, reducing the time spent on manual analysis and enabling data-driven insights.
--timeframe, with options like 7d, 2w, 1m, sprint, or custom date ranges.md) or HTML (html) format.Run the following command to generate a markdown report for the last 7 days:
ck retro --timeframe 7d
High-intent search queries and answers about installing and using this skill.
You can automate sprint retrospective report generation by computing git metrics like commit frequency, code churn, and file hotspots to produce a structured markdown or HTML report. This reduces manual analysis time and provides data-driven insights.
Data-driven retrospectives analyze git metrics such as commit frequency, code churn, file hotspots, and commit distribution. These code health indicators are automatically extracted from your git history to highlight performance trends.
Yes, retrospective report generation works with GitHub issues tracking by optionally utilizing the gh command-line tool. While git is required for core commit and code churn analysis, gh integration allows you to pull additional issue data into the report.
Yes, you can generate a markdown or HTML retrospective report for a custom date range. The tool supports configurable timeframes, allowing you to use preset options like 7d, 2w, 1m, sprint, or specify custom date ranges via flags.
The best way to analyze code churn and file hotspots for a sprint is to run an automated git metrics analysis over your selected timeframe. This automatically computes the data and structures it into a detailed report highlighting code health indicators.
Yes, you need git installed to generate code health and retrospective reports because it is the required dependency for extracting commit history and code churn data. The gh tool is optional and only needed for GitHub issues tracking.
khapn-2933Generate sprint retrospective reports from git repository history.
duy-tungGenerate sprint retrospective reports from Git history with metrics and recommendations.
zzafergokConvert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators.
bitwardenGenerate structured retrospective reports from Claude Code session data.