retro

Analyze Git history to generate weekly engineering retrospectives with per-author metrics.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/shihwesley/shihwesleys-harness --skill retro-shihwesley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/shihwesley/shihwesleys-harness/tree/main/skills/gstack/retro
Command: npx skills add https://github.com/shihwesley/shihwesleys-harness --skill retro-shihwesley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are time-consuming and inconsistently tracked; this skill automates collection, analysis, and narrative generation from VCS history to produce a cohesive, team-aware retro.

Core Features & Use Cases

  • Analyzes commit history and authors to identify contributions, patterns, and growth opportunities.
  • Generates per-author breakdowns, time-series trends, and focus metrics to inform planning.
  • Produces a narrative that explains team health, shipping velocity, and areas for improvement for leadership review.

Quick Start

Run the retro skill for the last 7 days to generate a weekly summary.

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?

Engineering retrospectives analyze Git commit data to calculate per-author statistics, time-based patterns, and team contributions. This skill parses VCS history to assemble metrics like commits, LOC, tests, and PRs into a narrative summary suitable for leadership review.

Can I track per-person engineering contributions and team performance metrics automatically?

Track per-person engineering contributions automatically by parsing Git commit history to calculate per-author statistics. The skill identifies individual contributions, focus areas, and growth opportunities, producing tabular metrics and a narrative explaining overall team health and shipping velocity.

Does this tool work for analyzing engineering team performance of any size?

Yes, this tool works for analyzing engineering team performance of any size. It parses commit data and PR history to calculate per-author statistics and time-series trends, generating a cohesive, team-aware retrospective regardless of how many developers are contributing.

What is the best way to automate code activity analysis for leadership review?

The best way to automate code activity analysis for leadership review is parsing VCS history to generate a narrative summary of team health. This skill transforms weekly commit data, shipping velocity, and focus metrics into a cohesive narrative explaining trends and areas for improvement.

How do I calculate per-author statistics and focus areas from commit data?

Calculate per-author statistics from commit data by parsing Git history to identify individual contributions and time-based patterns. The skill assembles metrics such as commits, LOC, tests, and PRs into per-author breakdowns, highlighting specific focus areas and opportunities for growth.

What metrics are included in a Git-based engineering retrospective?

A Git-based engineering retrospective includes metrics such as commits, LOC, tests, and PRs. It calculates per-author statistics, time-series trends, and focus areas to produce both tabular metrics and a narrative summary explaining team health and shipping velocity.