ck:retro

Generate retrospective reports from git history with commits, LOC, hotspots, and churn.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/hidonguyen/trade-ops --skill ck-retro-hidonguyen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:retro
Source: https://github.com/hidonguyen/trade-ops/tree/main/.opencode/skills/retro
Command: npx skills add https://github.com/hidonguyen/trade-ops --skill ck-retro-hidonguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provide objective, data-driven retrospectives by extracting measurable git metrics so teams avoid subjective guesswork and base sprint reviews on verifiable activity.

Core Features & Use Cases

  • Automated Git Metrics: Collect commits, LOC added/removed, net LOC, file hotspots, churn, commit type distribution, active days, and per-author breakdowns.
  • Health Indicators & Comparisons: Compute derived metrics (commit frequency, churn rate, test-to-code ratio, active-day ratio) and optionally compare to a preceding period.
  • Plan and Issue Checks: Scan plans/ for checkbox progress and optionally use gh to count closed issues; export structured reports as Markdown or self-contained HTML.
  • Use Cases: Run after a sprint, for weekly check-ins, or for ad-hoc reviews to identify hotspots, test coverage trends, and plan completion rates with concrete recommendations.

Quick Start

Run ck:retro with a timeframe (e.g., 7d, 1m, or YYYY-MM-DD:YYYY-MM-DD) and optional flags like --compare or --team to generate a retrospective report from the repository git history.

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

You can generate a data-driven retrospective from git history by computing commits, LOC added or removed, file hotspots, and churn rates for a specified timeframe. This extracts verifiable repository metrics to base sprint reviews on objective activity rather than subjective guesswork.

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

Code health metrics indicating issues include file hotspots showing frequent changes, high churn rates, commit type distribution, and the test-to-code ratio. Monitoring these metrics helps identify unstable areas and test coverage trends for concrete development recommendations.

How do I compare git metrics between two different time periods?

To compare git metrics between two time periods, apply a comparison flag to the retrospective generation process against a preceding period. This computes derived metrics like commit frequency, churn rate, and active-day ratios to show development trends over time.

Do I need the gh CLI to generate retrospective reports with per-author breakdowns?

You do not need the gh CLI to generate retrospective reports with per-author breakdowns, as standard git history provides sufficient data. The gh CLI is an optional dependency used to count closed issues if you want to track GitHub plan completion progress.

Can I export git retrospective reports as self-contained HTML or Markdown?

Yes, you can export git retrospective reports as structured Markdown or self-contained HTML files. The reporting process scans plans for checkbox progress and formats the collected repository metrics into portable document formats for team distribution.