skills.rest
caraseli02
caraseli02COMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze git history to generate weekly engineering retrospectives with per-author stats.

Updated Aug 27, 2026
Search Tags:#git#metrics#engineering#code-quality#retro#team-performance
One-click install
npx skills add https://github.com/caraseli02/MoldovaDirect --skill retro-caraseli02
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/caraseli02/MoldovaDirect/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/caraseli02/MoldovaDirect --skill retro-caraseli02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives from git history are difficult to assemble manually; this skill automates generating a team-wide weekly engineering retrospective with per-person contributions, praise, and growth opportunities, preserving context across weeks.

Core Features & Use Cases

  • Analyzes commit history, work patterns, and code quality metrics to produce a team-wide retrospective.
  • Keeps a persistent history and trend data to reveal improvement or regression over multiple weeks.
  • Provides a narrative summary for leadership and a structured data snapshot for archival or reporting.

Quick Start

Ask Claude to run /retro for the default 7-day window to generate this week's retrospective.

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

To generate a weekly engineering retrospective from git history, you can run the /retro command to analyze a repository's default branch over a configurable time window. It automatically computes per-author commits, insertions, and deletions to produce the report.

Can I track code-quality trends and team performance over multiple weeks?▼

Yes, you can track code-quality trends and team performance over multiple weeks. The skill maintains a persistent history of trend data to reveal improvement or regression, providing growth insights and narrative summaries for leadership.

Does the retrospective tool require a specific default branch or time window?▼

The retrospective tool analyzes the repository's default branch and uses a configurable time window. By default, it targets a 7-day window for sprint reviews and weekly summaries, but this period can be adjusted as needed.

What is the best way to surface individual contributions for sprint reviews?▼

The best way to surface individual contributions for sprint reviews is to analyze commit work patterns and compute per-author statistics. This approach generates a team-wide retrospective with per-person praise and growth opportunities.

How do I get a structured data snapshot for engineering reporting?▼

To get a structured data snapshot for engineering reporting, run the /retro command on your git history. It computes shipping activity and code-quality metrics, outputting both a narrative summary for leadership and a structured snapshot for archival.

Related Skills

Explore More Software Engineering Skills→
Cogni-AI-OUCogni-AI-OU
3

git-filter-branch

Extract a subdirectory's commit history using git-filter-branch and merge it into another repository.

Official
Intermediate
weirdgmeweirdgme
4

platform-engineering

Design and implement scalable platform engineering patterns for internal developer platforms.

Community
Advanced
ysyecustysyecust
40

springboot-verification

Verify Spring Boot projects with builds, static analysis, tests, and security scans.

Community
Advanced
fghaffarfghaffar

retro

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

Community
Advanced