retro

Analyze git commit history and code quality metrics to generate weekly retrospectives.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill retro-caltexbevo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/gstack.bak/retro
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill retro-caltexbevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that surface actionable insights from commit history, work patterns, and code quality, helping teams reflect and improve.

Core Features & Use Cases

  • Persistent, team-aware analysis that breaks down per-person contributions with praise and growth opportunities.
  • Trend tracking across sprints to identify improvements, patterns, and risks in code quality and collaboration.
  • Actionable takeaways for process, testing, and delivery that can be prioritized in future sprint planning.

Quick Start

Run /retro to generate a weekly retro for your current repository.

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 history?

Generate a weekly engineering retrospective by parsing your git history to aggregate per-author metrics, work patterns, and code quality data into a persistent summary. Run the /retro command to automatically analyze your current repository and produce this actionable report highlighting praises and growth opportunities.

What is a git commit history analysis for team performance?

Git commit history analysis for team performance identifies engineering work patterns by aggregating per-author metrics and code quality trends. It summarizes contributions across weekly sprints, highlighting individual praises and growth opportunities to help your team reflect and improve delivery processes.

Can I track code quality metrics and work patterns across multiple sprints?

Yes, you can track code quality metrics and work patterns across multiple sprints by applying the analysis to weekly sprints and project milestones. This persistent tracking compares performance across time and teammates to identify risks, collaboration patterns, and improvements.

How do I get actionable takeaways from per-author code metrics for sprint planning?

Get actionable takeaways for sprint planning by aggregating per-author code metrics to highlight process, testing, and delivery risks. The analysis breaks down individual contributions into specific praises and growth opportunities that can be directly prioritized in future planning sessions.

Do I need any external dependencies to run retrospectives on my repository?

No external dependencies are required to run engineering retrospectives on your repository. The skill operates independently to parse your git history and aggregate code quality metrics without needing additional components or external tools installed.