One-click install
npx skills add https://github.com/ByronWilliamsCPA/.claude --skill retro-byronwilliamscpa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/ByronWilliamsCPA/.claude/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/ByronWilliamsCPA/.claude --skill retro-byronwilliamscpa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually compiling development metrics for team retros is time-consuming and often relies on anecdotes instead of actual git data, leading to inaccurate or biased insights.

Core Features & Use Cases

  • Git History Analytics: Mines local git logs to compute commit cadence, per-author contribution, churn hotspots, PR cycle time, and Conventional Commit type distribution.
  • Trend Comparison: Calculates deltas against a prior equal-length window to spot shifts in development velocity or effort allocation.
  • Use Case: After a sprint, use this skill to quickly identify if a file like src/auth/session.py is a recurring churn hotspot, or if the commit mix shifted heavily to fix entries following a release.

Quick Start

Use the retro skill to generate an engineering retro for the last 14 days of development activity.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate engineering retrospective metrics from git logs?

To generate engineering retrospective metrics from git logs, you can use this skill to mine local repository history and compute commit cadence, per-author contribution, churn hotspots, and PR cycle time for sprint closeouts.

Can I track commit cadence and churn hotspots for a sprint review?

Yes, you can track commit cadence and identify churn hotspots for sprint reviews by analyzing git log data. This skill calculates these metrics and identifies files with high modification frequency to highlight recurring development issues.

What is a git development retrospective and how does trend comparison work?

A git development retrospective analyzes repository history to evaluate team velocity and effort allocation. Trend comparison works by calculating metric deltas against a prior equal-length window to spot shifts in development patterns.

Does this work with Conventional Commit type distribution analysis?

Yes, this works with Conventional Commit type distribution analysis by parsing native git log data. It categorizes commits by type to show if your commit mix shifted heavily to fix entries or feature additions following a release.

Do I need external dependencies or CI tools to calculate PR cycle time?

No, you do not need external dependencies or CI tools to calculate PR cycle time. This skill computes cycle time and development velocity tracking metrics using only native git log data from your local repository.

What's the best way to identify churn hotspots in a local git repository?

The best way to identify churn hotspots in a local git repository is to analyze commit history for files with high modification frequency. This skill automates that investigation by mining git logs to pinpoint recurring problem files.