skills.rest
Duy-Nguyen-2006
Duy-Nguyen-2006COMMUNITY
Explore all skills by this author →
GitHub

ck:retro

Generate structured sprint retrospective reports from git repository metrics.

Updated Aug 27, 2026
Search Tags:#git#report generation#metrics#retrospective#sprint planning
One-click install
npx skills add https://github.com/Duy-Nguyen-2006/Claudev --skill ck-retro-duy-nguyen-2006
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:retro
Source: https://github.com/Duy-Nguyen-2006/Claudev/tree/main/claude/skills/retro
Command: npx skills add https://github.com/Duy-Nguyen-2006/Claudev --skill ck-retro-duy-nguyen-2006

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a structured and data-driven approach to sprint retrospectives by automating the collection of git metrics and generating detailed reports.

Core Features & Use Cases

  • Git Metrics Collection: Gathers commit frequency, code churn, file hotspots, and more.
  • Health Indicators Calculation: Computes metrics like commit frequency, test-to-code ratio, and churn rate.
  • Report Generation: Outputs a markdown or HTML report that includes a summary, velocity metrics, code health, and team breakdown.

Quick Start

Generate a retrospective report for the last sprint using the ck:retro skill.

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 sprint retrospective report from git history?▼

To generate a sprint retrospective report from git history, you can use this Skill to analyze commit frequency, code churn, and file hotspots, outputting a structured markdown or HTML report for review.

What git metrics should I track for a data-driven retrospective?▼

For a data-driven retrospective, you should track git metrics like commit frequency, code churn rate, file hotspots, and test-to-code ratio to calculate code health and team velocity indicators.

Can I output retrospective metrics as markdown or HTML for team discussion?▼

Yes, you can output retrospective metrics as markdown or HTML files, which include summary data, velocity metrics, code health indicators, and team breakdowns for team discussion and review.

Does this approach require any specific dependencies to analyze repository data?▼

No, this approach to analyzing repository data requires no specific dependencies, allowing you to directly extract git metrics and generate structured retrospective reports from your existing repository history.

What is the best way to identify file hotspots and code churn during a sprint?▼

The best way to identify file hotspots and code churn during a sprint is by analyzing git repository history to calculate health indicators and highlight areas with high modification frequency for review.

Related Skills

Explore More Software Engineering Skills→
cobusgreylingcobusgreyling
10.0k

changelog-scan

Extract PR and commit information into a structured release notes draft.

Community
Intermediate
khapn-2933khapn-2933

tkm:run-retro

Generate sprint retrospective reports from git repository history.

Community
Advanced
C0ntr0lledCha0sC0ntr0lledCha0s
3

planning-sprints

Automate sprint planning and backlog refinement with prioritization frameworks.

Community
Intermediate
rm2thaddeusrm2thaddeus
4

code-auditor

Analyze codebases for architecture, quality, security, performance, and maintainability.

Community
Advanced