Verified:GitHub

retro

Analyzes tracked time and generates weekly reports for managers and teams, highlighting progress and areas for attention.

Updated Feb 27, 2026

Search Tags:#git #analysis #metrics #engineering #team #retro

Ready to run

npx skills add https://github.com/zhifengzhang-sz/divine-book --skill retro-zhifengzhang-sz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/zhifengzhang-sz/divine-book/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/zhifengzhang-sz/divine-book --skill retro-zhifengzhang-sz

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This weekly retrospective analyzes commit history, work patterns, and code quality metrics to surface team-wide insights, praise, and growth opportunities, helping teams improve over time.

## Core Features & Use Cases

Per-person praise and growth recommendations based on contribution patterns across a persisted history.
Trend tracking to reveal performance trajectories, collaboration dynamics, and process improvements.
Team-aware retrospectives for weekly sprints, project handoffs, and cross-project learning.

### Quick Start Ask Claude to run /retro to generate the weekly retrospective and per-person growth notes.

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

You can generate an engineering retrospective from git commit history by analyzing work patterns and code quality metrics to produce team-wide insights, praise, and growth recommendations. This tool parses local project data deterministically to ensure repeatable results.

What is a team-aware engineering retrospective and how does it work?▼

A team-aware engineering retrospective analyzes contribution patterns across persisted local project history to surface per-person praise and growth recommendations. It tracks trends to reveal performance trajectories, collaboration dynamics, and process improvements over time.

Can I compare engineering metrics across different time periods or projects?▼

Yes, you can compare engineering metrics across different time periods or projects. The retrospective tool compares weekly windows and performs cross-project retrospectives, yielding per-person observations and trend data to identify performance trajectories and collaboration dynamics.

How do I track team performance trends and collaboration dynamics?▼

You track team performance trends and collaboration dynamics by analyzing commit history and work patterns over weekly windows. The retrospective tool reveals performance trajectories, collaboration dynamics, and process improvements through structured reporting and trend data.

Does the engineering retrospective tool require any external dependencies or APIs?▼

No, the engineering retrospective tool requires no external dependencies or APIs. It relies entirely on local project data, deterministic parsing, and structured reporting to ensure repeatable results and actionable recommendations.

What's the best way to run a weekly sprint retrospective for engineering teams?▼

The best way to run a weekly sprint retrospective is to analyze commit history and code quality metrics over a default 7-day window. This produces team-aware insights with per-person growth notes, making it ideal for weekly sprints, project handoffs, and cross-project learning.