skills.rest
bhianerd
bhianerdCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze git commit history to generate weekly engineering retrospectives.

1|Updated Mar 25, 2026
Search Tags:#code-quality#git-analysis#testing-metrics#team-contributions#engineering-retro#commit-trends
One-click install
npx skills add https://github.com/bhianerd/aimemory --skill retro-bhianerd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/bhianerd/aimemory/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/bhianerd/aimemory --skill retro-bhianerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams stop guessing and instead understand what was shipped, how work was distributed, and how code quality is trending over time.

Core Features & Use Cases

  • Weekly engineering retrospective: Analyzes commit history for shipping velocity, code churn, and quality signals within a chosen time window.
  • Team-aware insights: Breaks down contributions by person, including praise anchored in actual commits and growth opportunities tied to observed metrics.
  • Trends & history: When enough time has passed, compares week-over-week and records snapshots so improvements (or regressions) are visible.
  • Optionally global retrospective: Produces cross-project retros across AI coding tools when invoked in global mode.

Quick Start

Ask your AI assistant for: /retro to generate a retrospective for the last 7 days.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate an engineering retrospective from git commit history?▼

Generate an engineering retrospective by triggering a command that analyzes git commit history, work patterns, and code quality metrics within a specified time window. It computes shipping velocity, code churn, and LOC to test ratios for your team.

Can I track week-over-week code quality trends and team contributions?▼

Track week-over-week code quality trends by comparing saved retro snapshots over time. The retrospective analyzes team contributions per person, highlighting praise from actual commits and growth opportunities tied to observed metrics.

What is a global retrospective for cross-project development reviews?▼

A global retrospective produces cross-project engineering reviews across AI coding tools when invoked in global mode. It analyzes commit trends and work patterns spanning multiple projects within your chosen time window.

Does the weekly shipping retrospective require manual trigger invocation?▼

Weekly shipping retrospectives require manual trigger invocation to analyze the last 7 days. You can also use windowed modes including compare and global to analyze different time frames and compute session patterns, hotspots, and streaks.

What code quality metrics are computed in a team-based development review?▼

Team-based development reviews compute metrics such as LOC to test ratios, session patterns, hotspots, and streaks. These code quality metrics are derived directly from git commit history and work distribution within the specified window.

Related Skills

Explore More Software Engineering Skills→
cegit27cegit27
3

retro

Analyze git commit history to generate weekly retrospective reports.

Official
Advanced
aiunlocked1412aiunlocked1412
14

agile-coach

Generate sprint planning packages with capacity calculations and ceremony scripts.

Community
Intermediate
JeremiahEllingtonJeremiahEllington

retro

Analyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.

Community
Advanced
HouseofmvpsHouseofmvps
115

retro

Analyze git repository history to generate structured sprint retrospective reports.

Community
Intermediate