skills.rest
huichen
huichenCOMMUNITY
Explore all skills by this author →
GitHub

retro

Parse Git history and commit metadata to summarize engineering activity.

Updated Mar 31, 2026
Search Tags:#git#analysis#metrics#retrospective#engineering#leadership#team
One-click install
npx skills add https://github.com/huichen/gstack --skill retro-huichen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/huichen/gstack/tree/main/retro
Command: npx skills add https://github.com/huichen/gstack --skill retro-huichen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that synthesize commit history, code quality signals, and team dynamics into a clear narrative with actionable growth opportunities.

Core Features & Use Cases

  • Analyzes commits, author activity, and trend metrics to surface per-person praise and growth areas.
  • Generates a team-aware retrospective that helps engineering leadership plan improvements and celebrate wins.
  • Supports a cross-project perspective to compare team performance over time.

Quick Start

Run /retro to generate the current week's engineering retrospective for your repository.

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

Generate an engineering retrospective by running a command that parses Git history and commit metadata to compute per-author contributions and team-wide trend metrics. It outputs a structured summary with a leaderboard and a narrative suitable for executives.

Can I analyze code-quality signals and commit metadata for weekly team performance?▼

Yes, you can analyze code-quality signals and commit metadata to evaluate weekly team performance. The analysis computes per-author praise and growth opportunities, surfacing team dynamics and actionable insights for engineering leadership.

What is the best way to summarize per-author contributions for engineering leadership?▼

The best way to summarize per-author contributions is to synthesize commit activity into a structured, embed-friendly summary. This includes a per-author leaderboard and overall metrics, helping leadership plan improvements and celebrate wins.

Does the retrospective analysis support cross-project performance comparisons?▼

Yes, the retrospective analysis supports cross-project performance comparisons. It provides optional global-retro data, allowing you to compare team performance and momentum trends over time across different projects.

How do team-aware retrospectives help plan engineering improvements?▼

Team-aware retrospectives help plan engineering improvements by synthesizing commit history and team dynamics into a clear narrative. This narrative highlights actionable growth opportunities and per-person praise to guide leadership decisions.

Related Skills

Explore More Software Engineering Skills→
weisser-devweisser-dev
22

changelog-generate

Generate CHANGELOG.md from git history using Keep a Changelog format.

Community
Intermediate
s23hs23h

report-style-guide

Generate self-contained HTML data reports with metrics dashboards and charts.

Community
Intermediate
viraatdasviraatdas

retro

Analyze git commit history and contribution metrics to generate weekly team retrospectives.

Community
Advanced
fghaffarfghaffar

retro

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

Community
Advanced