skills.rest
ignidus
ignidusOFFICIAL
Explore all skills by this author →
WebsiteGitHub

retro

Analyze Git repository history to produce a data-driven retro report.

Updated Mar 18, 2026
Search Tags:#git#analytics#productivity#metrics#velocity#team#retro
One-click install
npx skills add https://github.com/ignidus/iscagent --skill retro-ignidus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/ignidus/iscagent/tree/main/skills/retro
Command: npx skills add https://github.com/ignidus/iscagent --skill retro-ignidus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Retro skill provides a structured way to transform Git history into actionable insights about team velocity, code quality, and contributor activity, enabling data-driven sprint reflections.

Core Features & Use Cases

  • Data-driven velocity and quality metrics derived from commits, PRs, and file changes.
  • Weekly narratives and trend analysis suitable for sprint reviews and team health checks.
  • Use Case: A manager runs a weekly retro to identify bottlenecks and prioritize improvements for the next sprint.

Quick Start

Run the retro skill against your repository to generate a weekly retrospective report.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate team velocity metrics from git history for a sprint review?▼

Generate team velocity metrics by analyzing git history, PR activity, and contributor activity to produce a structured narrative report suitable for weekly sprint reviews. The analysis computes data-driven metrics directly from repository commits and file changes.

What is a data-driven engineering retrospective and how does git analysis work for it?▼

A data-driven engineering retrospective transforms git commit history, PR activity, and file changes into actionable insights about team velocity, code quality, and contribution patterns. It computes metrics from repository data to highlight project health trends.

Can I analyze multiple git repositories to assess engineering productivity and project health?▼

Yes, you can analyze multiple git repositories to assess engineering productivity and project health. The analysis processes contributor activity and code quality patterns across repos to produce trend narratives for team health checks.

What's the best way to identify development bottlenecks from commit history and PR activity?▼

Identify development bottlenecks by computing velocity, quality, and contribution metrics from commit history and PR activity. This generates a weekly retrospective report highlighting patterns and bottlenecks to prioritize improvements for the next sprint.

Does the git retrospective analysis require any external dependencies or components?▼

No external dependencies or components are required to run the git retrospective analysis. It operates directly on your repository history to compute metrics and present results in a structured narrative format.

When should I use git analytics for a team retrospective instead of manual sprint reviews?▼

Use git analytics for team retrospectives when you need data-driven velocity and quality metrics derived from commits, PRs, and file changes. It is applicable for weekly sprint reviews, project health assessments, and engineering analytics across multiple repos.

Related Skills

Explore More Software Engineering Skills→
bswrundquistbswrundquist

git-analyze

Analyze git repository history for activity, initiatives, bugs, and contributors.

Community
Advanced
tumestumes

retro

Analyze completed sprints to identify velocity trends, scope changes, and blocker patterns.

Community
Advanced
pskoettpskoett
273

dx-data-navigator

Query the DX Data Cloud PostgreSQL database to analyze developer productivity and engineering metrics.

Community
Advanced
jangtrinhjangtrinh

retro

Analyze Git history to generate retrospective reports with sprint metrics.

Community
Advanced