skills.rest
olaafrossi
olaafrossiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze weekly commit history and code quality metrics into a structured retro report.

10|3|Updated Mar 25, 2026
Search Tags:#git#analytics#metrics#engineering#code-quality#retro#team-performance
One-click install
npx skills add https://github.com/olaafrossi/FoamPilot --skill retro-olaafrossi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/olaafrossi/FoamPilot/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/olaafrossi/FoamPilot --skill retro-olaafrossi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives are time-consuming to assemble from raw Git data and team signals. This Skill automates the collection and synthesis of commit history, contribution patterns, and code-quality indicators into a structured, shareable report.

Core Features & Use Cases

  • Analyzes commit history, per-user contributions, and code-quality metrics with a persistent history to track trends over time.
  • Highlights praise and growth opportunities per contributor, helping teams focus on improvement.
  • Proactively suggests retrospective topics and questions at the end of each work cycle to drive continuous improvement.

Quick Start

Type /retro to generate a weekly engineering 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 automate weekly Git retrospectives from commit history and code quality metrics?▼

You can automate weekly Git retrospectives by analyzing commit history, team patterns, and code quality metrics to produce a structured, shareable report. It summarizes per-person contributions, praise, and growth areas with trend tracking over time.

How do I track engineering team performance trends over time using Git data?▼

Track engineering team performance by maintaining a persistent history of weekly commit analysis and code-quality metrics. This allows you to monitor contributor patterns, highlight growth opportunities, and visualize performance trends across multiple work cycles.

Can I generate per-contributor code quality and praise summaries from commit data?▼

Yes, you can generate per-contributor summaries from commit data that highlight individual praise and growth opportunities. It analyzes per-user contribution patterns and code-quality indicators to help teams focus on continuous improvement.

What is the best way to summarize team performance and suggest retro topics from code history?▼

Summarize team performance and suggest retro topics by analyzing weekly commit history and code-quality metrics. The output proactively suggests retrospective topics and questions at the end of each work cycle to drive continuous improvement.

How does the retrospective analysis handle missing data and forks in Git history?▼

The retrospective analysis handles missing data and forks gracefully by detecting gaps in commit history and managing branch divergences. This ensures the structured output focuses on actionable insights without failing on incomplete repository data.

Related Skills

Explore More Software Engineering Skills→
blakeoxblakeox

retro

Analyze git history to generate engineering team retrospective reports.

Community
Intermediate
davepoondavepoon
3.3k

developer-growth-analysis

Analyze Claude Code chat history to identify coding patterns and development gaps.

Community
Advanced
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced
fghaffarfghaffar

retro

Generate weekly engineering retrospective reports from Git commit history and metrics.

Community
Advanced