skills.rest
snake-dev-team
snake-dev-teamOFFICIAL
Explore all skills by this author →
GitHub

ck:retro

Extract git history and generate sprint retrospective reports in markdown or HTML.

Updated Apr 23, 2026
Search Tags:#project management#retrospective#code health#sprint analysis#git metrics
One-click install
npx skills add https://github.com/snake-dev-team/snake-backlink-forge --skill ck-retro-snake-dev-team
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:retro
Source: https://github.com/snake-dev-team/snake-backlink-forge/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/snake-dev-team/snake-backlink-forge --skill ck-retro-snake-dev-team

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the collection of git metrics, computation of health indicators, and generation of structured reports, making data-driven sprint retrospectives efficient and effective.

Core Features & Use Cases

  • Git Metrics Analysis: Gathers information on commits, lines of code, and authorship.
  • Health Indicators: Computes derived metrics such as commit frequency, churn rate, and test-to-code ratio.
  • Structured Reporting: Generates markdown or HTML reports with actionable recommendations based on the analysis.

Quick Start

Run the retro skill with the current sprint timeframe to get a report on project progress and health.

Frequently Asked Questions about ck:retro

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

FAQPage Schema
How do I automate sprint retrospective analysis using git metrics?▼

Automate sprint retrospective analysis by extracting git history to compute code health, velocity, and plan completion metrics. This Skill generates structured markdown or HTML reports with actionable recommendations based on commit frequency and churn rate.

What git metrics are used to calculate code health for a sprint review?▼

Code health indicators for sprint reviews are calculated using git metrics such as commit frequency, lines of code, authorship, and test-to-code ratio. These derived metrics help evaluate project progress and identify potential issues during the sprint timeframe.

Do I need the GitHub CLI to generate retrospective reports for my repository?▼

The GitHub CLI is optional for generating retrospective reports and is used specifically for issue tracking. You only need git repository access to extract commit history and compute health indicators for your sprint analysis.

Can I export sprint velocity and churn rate data into structured markdown reports?▼

Yes, you can export sprint velocity and churn rate data into structured markdown or HTML reports. The Skill computes derived metrics from git history and outputs actionable recommendations in your chosen format for efficient data-driven retrospectives.

How does automated git history extraction work for project management retrospectives?▼

Automated git history extraction for project management retrospectives works by running git commands to gather commits, lines of code, and authorship data. It then computes health indicators like churn rate and generates structured reports with actionable insights.

Related Skills

Explore More Software Engineering Skills→
josephneumannjosephneumann
4

retro

Analyze Git commit history to generate engineering retrospective reports.

Community
Advanced
khapn-2933khapn-2933

tkm:run-retro

Generate sprint retrospective reports from git repository history.

Community
Advanced
janewilkinjanewilkin

test

Run pytest test suites and generate code coverage reports.

Community
Intermediate
Exia-thdExia-thd

project-manager

Plan and execute agile sprints, tasks, and risks for software teams.

Community
Advanced