skills.rest
EdgeHunt
EdgeHuntOFFICIAL
Explore all skills by this author →
GitHub

ck:retro

Analyze git metrics and generate structured retrospective reports.

Updated Apr 2, 2026
Search Tags:#metrics#retrospective#report#code-health#git-metrics#sprint-review#team-performance
One-click install
npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-retro-edgehunt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:retro
Source: https://github.com/EdgeHunt/EdgeHunt/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-retro-edgehunt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Data-driven sprint retrospectives help teams gather objective git metrics, identify hotspots, and turn metrics into a clear, actionable retrospective.

Core Features & Use Cases

  • Collects commits, LOC, hotspots, and churn
  • Computes derived health indicators and produces a structured markdown or HTML report
  • Use after sprints, weekly check-ins, or any review period to drive improvement

Quick Start

Analyze the most recent sprint and generate a markdown retrospective report.

Frequently Asked Questions about ck:retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a data-driven sprint retrospective from git metrics?▼

Generate a data-driven sprint retrospective by collecting objective git metrics like commits, LOC, and churn, then computing derived health indicators to produce a structured markdown or HTML report. This applies to sprints, weekly check-ins, or any specific date range.

What git metrics are used for measuring team performance during a sprint review?▼

Git metrics for team performance include commits, lines of code, hotspots, and code churn. These objective indicators are gathered deterministically via git commands and computed into derived health indicators to highlight activity hotspots and drive sprint reviews.

Can I analyze code health for a specific date range instead of a standard sprint?▼

Yes, you can analyze code health for a specific date range. The retrospective report supports flexible timeframes including 7d, 2w, 1m, standard sprint durations, or custom date ranges to accommodate weekly check-ins or any review period.

Does the retrospective report support team breakdown and historical comparison?▼

Yes, the retrospective report supports optional team breakdown and historical comparison. It computes objective git metrics and derived indicators, allowing you to compare performance across periods and segment the structured report by team.

What is the best way to identify code churn hotspots after a sprint?▼

The best way to identify code churn hotspots is to analyze sprint activity by collecting objective git metrics. The system computes churn and hotspot data, turning the metrics into a clear, actionable retrospective report to drive continuous improvement.

Are there limitations to using git metrics for sprint reviews?▼

Git metrics for sprint reviews are limited to deterministic data gathering via git commands. They provide objective indicators like commits and churn but do not capture qualitative team sentiment, requiring manual correlation for a complete retrospective.

Related Skills

Explore More Software Engineering Skills→
mike2oxmike2ox

my-retro

Create retrospective summaries from plan and review files with commit log analysis.

Community
Advanced
bitwardenbitwarden
129

retrospecting

Generate structured retrospective reports from Claude Code session data.

Official
Intermediate
Thanh-aperoThanh-apero
1

ck:retro

Generate markdown or HTML sprint retrospective reports from git metrics.

Community
Advanced
ZouZouZouZou

Dashboard & Analytics

Generate analytics dashboards for admins, instructors, and students.

Community
Advanced