skills.rest
duy-tung
duy-tungCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ck:retro

Generate sprint retrospective reports from Git history with metrics and recommendations.

Updated Jun 14, 2026
Search Tags:#git#metrics#retrospective#reporting#sprint
One-click install
npx skills add https://github.com/duy-tung/claude-code-setup --skill ck-retro-duy-tung
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:retro
Source: https://github.com/duy-tung/claude-code-setup/tree/main/claude/skills/retro
Command: npx skills add https://github.com/duy-tung/claude-code-setup --skill ck-retro-duy-tung

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automatically generates data-driven sprint retrospective reports from Git history, providing insights into team velocity, code health, and project progress.

Core Features & Use Cases

  • Data-Driven Retrospectives: Analyze Git activity to produce objective reports.
  • Customizable Timeframes: Analyze commits, LOC, and other metrics for any period.
  • Output Formats: Generate reports in Markdown or HTML for easy sharing.
  • Use Case: Use this Skill to review a sprint's performance, identify areas for improvement, and track progress over time.

Quick Start

Generate a sprint retrospective report for the last two weeks by running the command: ck:retro 2w.

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?▼

You can generate a sprint retrospective report from Git history by running the `ck:retro` command with a timeframe argument like `2w`, which analyzes commits and LOC to output team velocity and code health metrics in Markdown or HTML formats.

What metrics are included in an automated Git sprint report?▼

An automated Git sprint report includes insights into team velocity, code health, and project progress. These metrics are derived by analyzing historical commit activity and lines of code changes over a specified sprint period.

Can I customize the timeframe for Git retrospective metrics?▼

Yes, you can customize the timeframe for Git retrospective metrics. The Skill allows you to analyze commits, LOC, and other historical data for any specified period to review a sprint's performance and track progress over time.

Do I need bash access to automate sprint reporting from a Git repository?▼

Yes, you need bash access to automate sprint reporting from a Git repository. The Skill requires the ability to execute bash commands directly within the Git repository environment to analyze historical data and generate the report.

What is the best way to share sprint retrospective reports generated from Git activity?▼

The best way to share sprint retrospective reports generated from Git activity is by outputting them in Markdown or HTML formats. These formats allow for easy sharing and reviewing of team velocity and code health insights.

Related Skills

Explore More Software Engineering Skills→
gth-aigth-ai
1

retro

Analyze git commit history and code metrics to generate engineering retrospectives.

Community
Advanced
ev3rlitev3rlit

mermaid-kanban

Convert plain-text task lists into Mermaid Kanban diagrams with metadata.

Community
Intermediate
Thanh-aperoThanh-apero
1

ck:retro

Generate markdown or HTML sprint retrospective reports from git metrics.

Community
Advanced
emcconnellemcconnell

retrospective

Generate structured Markdown retrospectives from sprint plans and git commit history.

Community
Advanced