skills.rest
allen-hsu
allen-hsuCOMMUNITY
Explore all skills by this author →
GitHub

running-retro

Analyzes commit history to quantify weekly engineering activity and team performance metrics.

1|Updated Dec 31, 2025
Search Tags:#git#productivity#engineering#code-quality#commit-analysis#retro#team-metrics
One-click install
npx skills add https://github.com/allen-hsu/agent-arsenal --skill running-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: running-retro
Source: https://github.com/allen-hsu/agent-arsenal/tree/main/plugins/shipping/skills/running-retro
Command: npx skills add https://github.com/allen-hsu/agent-arsenal --skill running-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retros that analyze commit history, code quality, and team contributions to surface patterns, praise, and growth opportunities.

Core Features & Use Cases

  • Team-wide retrospective analysis: identifies contributors, hotspots, and focus areas; produces per-author summaries and a ship-of-the-week spotlight.
  • Data-driven insights: calculates commits, LOC, test coverage signals, session patterns, and time-based trends across the current window.
  • Guided narrative: outputs a structured recap and actionable recommendations to improve velocity and quality.

Quick Start

Ask Claude Code to run the weekly engineering retro for the current repository window.

Frequently Asked Questions about running-retro

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

FAQPage Schema
How do I generate a weekly engineering retro from git commit history?▼

You can analyze team contributions by reviewing the per-author leaderboard and contributor activity summaries generated from commit data. The Skill calculates individual commits, insertions, deletions, and test LOC to highlight specific contributor patterns and a ship-of-the-week spotlight.

What metrics are included in a commit analysis for engineering productivity?▼

Code quality signals such as test LOC, net LOC changes, and PR sizes are calculated directly from the commit history. These signals help identify code quality patterns and focus areas to improve engineering velocity across the repository window.

Can I run a team metrics retrospective for a specific repository window?▼

No external dependencies are required to use this Skill for engineering retros. It operates directly on your git repository's commit history and contributor activity to compute team metrics and produce the retrospective summary without needing additional components.

How does a git retrospective identify engineering hotspots and focus areas?▼

The Skill outputs a JSON snapshot containing computed metrics like total commits, net LOC, and active days, alongside a structured narrative recap. This guided narrative includes per-author summaries, a ship-of-the-week spotlight, and actionable recommendations to improve velocity and quality.

Related Skills

Explore More Software Engineering Skills→
MFS-codeMFS-code
8

retro

Generate weekly engineering retrospectives from git commit history and test signals.

Community
Advanced
BasharAmsoBasharAmso
1

Team Retro

Generates data-driven engineering retrospectives from Git commit history, TODOS, and DECISIONS.

Community
Advanced
JeffallanJeffallan
10.9k

Code Reviewer

Automate pull request reviews for code quality, security, and maintainability.

Community
Basic
viktorbezdekviktorbezdek
10

git-workflow

Automate Git commit formatting, branch organization, and release note generation.

Community
Advanced