skills.rest
madebynoam
madebynoamCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze origin/main commit history to generate weekly engineering retrospectives.

2|Updated Feb 9, 2026
Search Tags:#git#analysis#metrics#reporting#team#retro
One-click install
npx skills add https://github.com/madebynoam/bryllen --skill retro-madebynoam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/madebynoam/bryllen/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/madebynoam/bryllen --skill retro-madebynoam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams automatically synthesize a comprehensive retro from Git activity, highlighting contributions, patterns, and risks to guide improvements.

Core Features & Use Cases

  • Automated windowed retrospectives across last 7/14/30 days with per-author breakdowns.
  • Time-zone aware analysis of commits, sessions, and focus areas to reveal productive hours and bottlenecks.
  • Generated narrative highlighting focus, shipping velocity, and actionable growth opportunities for teammates.

Quick Start

Run a retro for the default window; output includes a narrative, metrics, and a snapshot you can review.

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

You can generate a weekly engineering retrospective by analyzing origin/main commit history to quantify activity and trends. The tool applies a configurable window to produce per-author metrics, time distribution, focus scores, and a narrative interpretation.

Can I customize the analysis window for Git activity metrics beyond the default?▼

Yes, Git activity metrics support a configurable analysis window with a default of 7 days. You can adjust this window to 14 or 30 days to synthesize comprehensive retrospectives across different timeframes.

What does a Git retrospective report include for engineering teams?▼

A Git retrospective report includes per-author metrics, time-zone aware commit session analysis, productive hours identification, and shipping velocity focus scores. It generates a structured snapshot with a narrative highlighting contributions, patterns, and risks.

Does the Git retrospective analysis work with repositories other than origin/main?▼

Git retrospective analysis specifically targets the origin/main commit history to quantify activity and trends. The tool relies on this branch data to extract time distribution and per-author metrics for the structured snapshot.

How are focus scores calculated from commit history?▼

Focus scores are calculated by analyzing commit sessions and time-zone aware activity patterns within the specified analysis window. This reveals productive hours and focus areas to identify bottlenecks and quantify shipping velocity.

What is the best way to run an automated team retrospective from code activity?▼

The best way to run an automated team retrospective is to analyze origin/main commit history with a configurable window. This automatically highlights individual contributions, reveals working patterns, and identifies actionable growth opportunities for teammates.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1

diff-analyze

Analyze git differences and commit history between the current branch and origin main.

Community
Basic
zz8011zz8011

retro

Analyze commit history and code-quality metrics to summarize weekly engineering retrospectives.

Community
Advanced
MissTullyMissTully

gstack-openclaw-retro

Analyze Git history and commit metadata to generate weekly engineering retrospectives.

Community
Advanced
HouseofmvpsHouseofmvps
115

retro

Analyze git repository history to generate structured sprint retrospective reports.

Community
Intermediate