ck:retro

Generate sprint retrospectives from git metrics using git and gh CLI.

1|Updated May 4, 2026

Search Tags:#git #metrics #retrospective #review #sprint

Ready to run

npx skills add https://github.com/auxi-wardrobe/auxi-all-in --skill ck-retro-auxi-wardrobe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ck:retro
Source: https://github.com/auxi-wardrobe/auxi-all-in/tree/main/.agents/skills/retro
Command: npx skills add https://github.com/auxi-wardrobe/auxi-all-in --skill ck-retro-auxi-wardrobe

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of data-driven sprint retrospectives, eliminating the need for manual analysis and providing actionable insights based on git metrics.

Core Features & Use Cases

Automated Retrospective Generation: Automatically generate retrospectives using objective git metrics.
Commit Analysis: Analyze commits, file changes, and authorship for insights.
Custom Reports: Generate HTML or Markdown reports with commit frequency, code health metrics, and team velocity.
Use Case: Ideal for engineering teams looking to quickly understand their sprint performance without manually sifting through commit history.

Quick Start

Run the ck:retro skill with the timeframe parameter to generate a report for the past week. Example: ck:retro 7d

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 from git metrics automatically?▼

You can generate a sprint retrospective automatically by running the skill with a specific timeframe parameter. It collects git metrics like commit frequency, code health, and team velocity using git and gh CLI to produce actionable insights without manual analysis.

What is data-driven sprint review and how does git commit analysis work?▼

Data-driven sprint review uses objective git metrics to evaluate performance instead of guesses. Git commit analysis works by parsing commit history, file changes, and authorship data to extract insights into team velocity and code health for the specified timeframe.

Do I need the gh CLI to run a git metrics retrospective?▼

Yes, you need both git and gh CLI installed to run a git metrics retrospective. The skill relies on these dependencies to collect commit history, analyze file changes, and extract authorship information required for the retrospective report.

Can I export a sprint review report as HTML or Markdown?▼

Yes, you can export custom sprint review reports as HTML or Markdown. The skill generates reports containing commit frequency, code health metrics, and team velocity based on the analyzed git data for your specified timeframe.

What's the best way to track team velocity using git commit history?▼

The best way to track team velocity using git commit history is to automate data collection over a specific timeframe. This skill analyzes commit frequency, file changes, and authorship to calculate objective velocity metrics for sprint retrospectives.