skills.rest
abustamam
abustamamCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze git history to summarize commits, LOC, tests, PRs, and per-author metrics.

Updated Feb 27, 2026
Search Tags:#analysis#metrics#engineering#team#git-history#retro
One-click install
npx skills add https://github.com/abustamam/portfolio-blog --skill retro-abustamam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/abustamam/portfolio-blog/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/abustamam/portfolio-blog --skill retro-abustamam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that surface contributions, patterns, and code-quality signals to improve team learning and performance.

Core Features & Use Cases

  • Team-aware metrics: aggregates commits, LOC, tests, PRs, and per-person contributions with growth notes.
  • Per-contributor focus: highlights strengths and opportunities for each teammate.
  • Historical continuity: persists snapshots to enable trend analysis over time.

Quick Start

Run the retro over origin/main for the last 7 days to generate a weekly snapshot.

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 origin/main for a specified time window to summarize commits, LOC, tests, and PRs. The skill computes per-author metrics and produces a narrative review with a structured JSON snapshot.

Can I analyze git history for a custom date range like 14 or 30 days?▼

You can analyze git history for custom date ranges including 14d and 30d windows. The retrospective skill applies to weekly windows or custom ranges to summarize commits, LOC, tests, and per-contributor focus over the specified period.

Does this approach require parsing origin/main to compute team metrics?▼

Yes, computing team metrics requires parsing origin/main to extract commit data. The skill analyzes this git history window to calculate per-author metrics, identify team contributions, and produce a structured JSON snapshot for historical continuity.

What's the best way to track engineering team contributions over time?▼

Track engineering team contributions over time by persisting structured JSON snapshots from each retrospective. Historical continuity enables trend analysis by saving weekly metrics on commits, LOC, tests, and PRs for comparison across multiple periods.

How does per-contributor focus work in a code retrospective?▼

Per-contributor focus in code retrospectives highlights individual strengths and growth opportunities. The skill aggregates commits, LOC, and tests per author to generate personalized notes, improving team learning and performance.

Related Skills

Explore More Software Engineering Skills→
ReviewStageReviewStage
259

rebase-origin-main

Rebase the current Git branch onto origin/main and resolve conflicts iteratively.

Official
Advanced
adelproadelpro
2

repo-metrics

Track GitHub repository metrics as JSON time-series for trend analysis.

Community
Intermediate
tranvietanh0tranvietanh0

t1k-retro

Analyze git metrics and generate sprint retrospective reports.

Community
Advanced
9thLevelSoftware9thLevelSoftware
1

github-sync

Integrate GitHub with Legion workflows for automated issue and milestone management.

Community
Advanced