skills.rest
nam3886
nam3886COMMUNITY
Explore all skills by this author →
GitHub

ck:retro

Analyze git history to generate retrospective reports with commit metrics.

Updated Aug 27, 2026
Search Tags:#git#metrics#retrospective#reporting#code-health#churn
One-click install
npx skills add https://github.com/nam3886/golang-echo-boilerplate --skill ck-retro-nam3886
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:retro
Source: https://github.com/nam3886/golang-echo-boilerplate/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/nam3886/golang-echo-boilerplate --skill ck-retro-nam3886

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill removes guesswork from retrospectives by extracting objective git-derived metrics and producing a concise, actionable report so teams can identify technical debt, hotspots, and delivery issues without manual data collection.

Core Features & Use Cases

  • Automated Git Metrics Collection: Runs git queries to gather commits, LOC added/removed, hotspots, churn, commit-type distribution, file and author activity.
  • Derived Health Indicators & Recommendations: Computes commit frequency, churn rate, test-to-code ratio, active day ratio, and plan completion, and produces targeted recommendations based on real data.
  • Report Generation: Renders a structured markdown report or a self-contained HTML file and saves it under plans/reports/ for sprint reviews, weekly check-ins, or post-incident analysis.

Quick Start

Analyze the last 7d and generate a markdown retrospective report that includes velocity, code health, hotspots, and 3 actionable recommendations.

Frequently Asked Questions about ck:retro

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

FAQPage Schema
How do I generate data-driven sprint retrospectives from git history?▼

Automate git metrics collection for sprint retrospectives by querying commits, LOC, churn, hotspots, and author activity to produce structured Markdown or self-contained HTML reports without manual data gathering.

What git metrics are used to measure code health and delivery velocity?▼

Measure code health and delivery velocity using git metrics like commit frequency, churn rate, test-to-code ratio, active days, file hotspots, and per-author activity breakdowns extracted directly from repository history.

Can I use the gh CLI to collect issue metrics for a custom date-range retrospective?▼

Yes, you can optionally use the gh CLI to collect issue metrics alongside local git repository activity for sprint, monthly, or custom date-range retrospective analysis and plan progress comparison.

How do I identify technical debt and code churn hotspots in a local repository?▼

Identify technical debt and code churn hotspots by analyzing local git repository history to extract file activity, churn rates, and commit-type distributions, rendering the findings into a concise actionable report.

Does this reporting approach require a remote repository or work completely offline?▼

This retrospective reporting approach operates on a local git repository to compute code health metrics and requires no remote connection, though you can optionally use the gh CLI to fetch issue metrics.

Related Skills

Explore More Software Engineering Skills→
26mitch2626mitch26

gstack-openclaw-retro

Analyze Git commit history to generate engineering retrospective reports.

Community
Advanced
bitwardenbitwarden
129

retrospecting

Generate structured retrospective reports from Claude Code session data.

Official
Intermediate
snake-dev-teamsnake-dev-team

ck:retro

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

Official
Advanced
billydeeii136billydeeii136

gstack-openclaw-retro

Generate engineering retrospectives and analyze code quality from git commit history.

Community
Advanced