skills.rest
cookys
cookysCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze Git history and sprint data to generate structured retrospective reports.

10|Updated Mar 18, 2026
Search Tags:#git#metrics#velocity#team-learning#retro#commit-patterns#sprint-analysis
One-click install
npx skills add https://github.com/cookys/autopilot --skill retro-cookys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/cookys/autopilot/tree/main/skills/retro
Command: npx skills add https://github.com/cookys/autopilot --skill retro-cookys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git history data often remains underutilized for team learning. This Skill enables data-driven retrospectives by extracting velocity trends, test ratios, and commit patterns from a repository.

Core Features & Use Cases

  • Data-driven sprint retrospectives: velocity, test ratio, focus, and commit pattern analysis.
  • Per-branch and per-project metrics to spot focus and fragmentation.
  • Visualizable outputs and structured retrospectives for team discussions.

Quick Start

Invoke the retro analysis for the current sprint to generate velocity, test ratio, focus, and commit-pattern insights.

Frequently Asked Questions about 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?▼

Generate a data-driven sprint retrospective by running git commands against your repository's origin history to extract velocity, test ratios, and commit patterns into a structured report. This process quantifies team learning and codebase health for sprint analysis.

What metrics can I extract from git commit patterns to measure team velocity?▼

You can extract velocity trends, test ratios, focus, and commit patterns from git history to measure team productivity. Per-branch and per-project metrics help spot focus fragmentation and quantify codebase health during release cycles.

Can I analyze per-branch git metrics to spot focus fragmentation during a release cycle?▼

Yes, you can analyze per-branch and per-project git metrics to spot focus and fragmentation during release cycles. This analysis identifies productivity patterns by quantifying velocity and commit patterns specific to each branch.

Do I need origin repository access to run git history analysis for sprint insights?▼

Yes, you need access to the repository's origin data to run git commands and collect metrics. This access is required to accurately extract commit patterns and velocity trends for the retrospective report.

What is the best way to quantify test ratio and codebase health from git history?▼

The best way to quantify test ratio and codebase health is by analyzing git history and sprint data together. This approach applies data-driven metrics to identify productivity patterns and output visualizable insights for retrospectives.

Related Skills

Explore More Software Engineering Skills→
alexandersumeralexandersumer
1

git-publish-to-origin

Commit and push the current Git branch to the origin repository with safety checks.

Community
Intermediate
tim-krausztim-krausz

retro-analysis

Generate team analytics retrospectives from notebooks, velocity, and reproducibility trends.

Community
Advanced
jorgeasaurusjorgeasaurus
12

openclaw-claude-mem

Configure persistent memory and observation feeds for OpenClaw gateways.

Community
Advanced
duy-tungduy-tung

ck:retro

Generate sprint retrospective reports from Git history with metrics and recommendations.

Community
Advanced