retro

Analyze git commit history to generate weekly retrospective reports with trend metrics.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/XDCIndia/SkyNet --skill retro-xdcindia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/XDCIndia/SkyNet/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/XDCIndia/SkyNet --skill retro-xdcindia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives are time-consuming and often miss data-driven insights; this skill automates gathering, analyzing, and presenting actionable metrics from code activity.

Core Features & Use Cases

  • Gathers commit history and computes velocity, code quality, and collaboration metrics.
  • Generates a narrative suitable for CTOs and engineers with focus signals, ship highlights, and weekly trends.
  • Use Case: Teams wanting objective weekly insights to inform planning and continuous improvement.

Quick Start

Type /retro to generate the latest weekly retro with the default 7-day window.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a weekly engineering retrospective from git commit history?

Generating a weekly engineering retrospective involves analyzing a software team's commit history across a multi-week window. The tool computes velocity, code quality, and collaboration metrics from commits, insertions, deletions, and test LOC to produce a structured report.

What metrics are included in an automated git retrospective report?

An automated git retrospective report includes team velocity, code quality, collaboration metrics, and focus scores. It detects coding sessions from commit timing and formats both a structured report and a tweetable summary for leadership and engineers.

Does this retrospective tool work with repositories not using origin/main?

The retrospective tool applies to projects using origin/main across multi-week windows. Repositories not using origin/main as their primary branch may not be fully supported for the default commit history analysis and trend detection.

Can I analyze coding sessions and focus scores from git data for my engineering team?

Yes, you can analyze coding sessions and focus scores from git data. The tool detects coding sessions from commit timing and computes focused insights, ship highlights, and weekly trends suitable for CTOs and engineers to inform planning.

What is the best way to automate team velocity reporting for engineering leadership?

The best way to automate team velocity reporting is by computing metrics directly from git data like commits, insertions, deletions, and test LOC. This approach provides objective weekly insights and a narrative summary formatted for leadership.

How do I get a tweetable summary of my team's weekly code activity?

You can get a tweetable summary of weekly code activity by running the retrospective tool with a default 7-day window. It analyzes commit history and formats a concise summary alongside the structured metrics report.