mint-retro

Quantify sprint retrospectives by analyzing Git history and commit activity.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill mint-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mint-retro
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/mint-retro
Command: npx skills add https://github.com/MINT-IA/MINT --skill mint-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Software teams often rely on qualitative retrospectives; this skill provides a quantitative lens by analyzing Git history, commits, tests, and hotspots to extract actionable learnings.

Core Features & Use Cases

  • Quantifies sprint activity (commits, tests, LOC) and identifies hotspots
  • Persists learnings across sessions for long-term memory and knowledge reuse
  • Generates structured retrospective reports suitable for stakeholders and future planning

Quick Start

Run a retro analysis with the default 7-day window to generate the first quantitative retrospective.

Frequently Asked Questions about mint-retro

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

FAQPage Schema
How do I generate a quantitative sprint retrospective from Git history?

To generate a quantitative sprint retrospective from Git history, you run an analysis on your commit activity to compute metrics like commits, tests, and lines of code. This surfaces hotspots and trends for sprint reviews.

What metrics can I extract from Git commits for a team retrospective?

You can extract metrics such as commit counts, test additions, and lines of code changes from Git commits. The analysis detects activity hotspots to highlight areas of intense development during the sprint.

Can I use Git commit analysis for end-of-week reviews and major PR milestones?

Yes, Git commit analysis is applicable for end-of-week reviews and major PR milestones. It processes commit activity within a specified time window, like the default 7-day period, to surface development trends and hotspots.

How do I persist learnings from a Git-based retrospective for future reference?

To persist learnings from a Git-based retrospective, the analysis stores the extracted insights across sessions. This provides long-term memory and knowledge reuse for future planning and stakeholder reporting.

Does a quantitative retrospective replace qualitative team discussions?

A quantitative retrospective does not replace qualitative discussions but provides a data-driven lens. It analyzes Git history, commits, and tests to extract actionable learnings, complementing traditional qualitative team retrospectives.