skills.rest
quanganh208
quanganh208COMMUNITY
Explore all skills by this author →
GitHub

ck:retro

Collect git metrics and generate structured retrospective reports in markdown or HTML.

1|Updated Mar 6, 2026
Search Tags:#automation#git#metrics#retrospective#velocity#code-health#churn
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-retro-quanganh208
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:retro
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/retro
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-retro-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates objective, data-driven sprint retrospectives by extracting git metrics and computing health indicators so teams can base reviews on verifiable facts rather than impressions.

Core Features & Use Cases

  • Automated Git Metrics: collects commits, LOC added/removed, file hotspots, churn, commit-type distribution, active days, and per-author breakdowns.
  • Derived Health Indicators: computes commit frequency, churn rate, test-to-code ratio, active day ratio, and plan completion signals with explicit formulas.
  • Report Generation & Comparison: fills a structured markdown report or a self-contained HTML page, supports preceding-period comparison and per-team breakdowns.
  • Use Case: run after a sprint or weekly check-in to surface high-churn files, low test coverage, uneven contribution, and generate 3–5 actionable recommendations.

Quick Start

Use ck:retro to analyze the last 7d and produce a markdown retrospective report including velocity, code health, hotspots, and 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 a data-driven sprint retrospective from git metrics?▼

To generate a data-driven sprint retrospective, you collect objective git metrics like commits, LOC, and file hotspots to compute health indicators and produce a structured markdown or HTML report. This replaces subjective impressions with verifiable facts for sprint reviews.

What git metrics indicate code health issues during a sprint review?▼

Key git metrics for code health include file churn rate, commit frequency, test-to-code ratio, and active day ratio. Analyzing these metrics helps surface high-churn files, low test coverage, and uneven contribution patterns for actionable recommendations.

How do I calculate plan completion and velocity using git history?▼

You calculate plan completion and velocity by analyzing git history commits alongside issue metrics from the gh CLI. The Skill computes these derived health indicators using explicit formulas to compare actual output against the sprint plan.

Can I use this retrospective tool with weekly or custom date ranges instead of sprints?▼

Yes, you can apply this retrospective tool to weekly check-ins or custom date ranges. It analyzes the specified period from your repository git history to compute commits, churn, and plan completion signals for any review cycle.

Does generating an automated retrospective report modify the repository?▼

Generating an automated retrospective report does not modify your repository. The process preserves read-only constraints while accessing git history and optionally the gh CLI to produce self-contained HTML or markdown outputs.

How do I compare sprint velocity and code churn against the previous period?▼

You compare sprint velocity and code churn against a preceding period by running the retrospective analysis across both date ranges. This generates a comparison report highlighting changes in commit frequency, hotspots, and contribution breakdowns.

Related Skills

Explore More Software Engineering Skills→
khapn-2933khapn-2933

tkm:run-retro

Generate sprint retrospective reports from git repository history.

Community
Advanced
open-octoopen-octo
88

artifact-design

Design self-contained HTML and Markdown artifacts for Octo's Artifacts panel.

Official
Intermediate
jangtrinhjangtrinh

ck:retro

Generate engineering retrospective reports from git history with Markdown or HTML output.

Community
Intermediate
JaykaijackJaykaijack

retro

Generate engineering retrospectives from git history and metrics.

Community
Advanced