skills.rest
hetsheth-droid
hetsheth-droidCOMMUNITY
Explore all skills by this author →
GitHub

retro

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives surface a clear narrative of how the codebase evolved by aggregating commit history, work patterns, and quality metrics. It highlights individual contributions, praises successes, and identifies growth opportunities for teammates, helping teams learn and improve over time.

Core Features & Use Cases

  • Team-aware retrospectives that summarize per-person contributions and growth opportunities.
  • Persistent history and trend tracking of code quality metrics across sprints.
  • Proactive, end-of-week prompts suggesting actions and improvements.
  • Supports requested views like /retro for weekly scope, /retro compare for window comparisons, and /retro global for cross-project insights.

Quick Start

Ask Claude Code to run /retro at the end of a sprint to generate the weekly retrospective for your team.

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

You can generate a weekly engineering retrospective by analyzing git commit history, work patterns, and code-quality metrics to produce a structured narrative with per-person praise and growth opportunities. Run /retro at the end of a sprint to automatically summarize your team's codebase evolution.

Can I compare code quality metrics across different sprint windows?▼

Yes, you can compare code quality metrics across different sprint windows using the /retro compare view. This feature allows you to track persistent history and trend changes in code quality metrics by analyzing git metadata and optional hotspot data across different time periods.

Does the weekly retro work with multi-repo projects for cross-team alignment?▼

Yes, the weekly retro supports multi-repo projects for cross-team alignment. You can use the /retro global view to aggregate commit history, work patterns, and engineering metrics across multiple projects, generating cross-project insights to align your entire engineering team.

What git metadata is needed to produce per-person engineering insights?▼

To produce per-person engineering insights, the retro analyzes git metadata including commit authors, commit timestamps, and commit history. It optionally leverages test data and hotspot data to generate team-aware narratives with individual contributions and growth opportunities.

How do team-aware retrospectives identify individual growth opportunities?▼

Team-aware retrospectives identify individual growth opportunities by analyzing per-person commit history and code-quality metrics to highlight specific areas for improvement. The retrospective output provides targeted praise and actionable suggestions for each teammate based on their engineering work patterns.

What is the best way to run a retro for a single repository project?▼

The best way to run a retro for a single repository project is to use the standard /retro command at the end of your weekly sprint window. This analyzes the repository's commit history and work patterns to generate a focused weekly engineering retrospective with actionable insights.

Related Skills

Explore More Software Engineering Skills→
borkwebborkweb
7

commit-writer

Generate conventional git commit messages from staged diffs and repository history.

Community
Intermediate
BradliebsBradliebs

retro

Analyze commit history and work patterns to generate weekly engineering retrospectives.

Community
Advanced
rshelekhovrshelekhov

retro

Analyze weekly Git activity to generate engineering retrospectives with per-author metrics.

Community
Advanced
robertzengcnrobertzengcn

retro

Analyze git commit history and code quality metrics to generate engineering retrospectives.

Community
Advanced