skills.rest
JovieInc
JovieIncOFFICIAL
Explore all skills by this author →
WebsiteGitHub

retro

Analyze git history windows to generate engineering retrospectives with per-author metrics.

Updated Aug 2, 2025
Search Tags:#git#analysis#metrics#engineering#team#retro
One-click install
npx skills add https://github.com/JovieInc/Jovie --skill retro-jovieinc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/JovieInc/Jovie/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/JovieInc/Jovie --skill retro-jovieinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to extract actionable insights from weekly activity and highlight growth opportunities; this Skill automates a comprehensive engineering retrospective.

Core Features & Use Cases

  • Per-person praise and growth recommendations based on commit history, code quality metrics, and activity patterns.
  • Team-wide retrospectives with persistent history and trend tracking suitable for CTO-level reviews.
  • A ready-to-share narrative that combines metrics, leaderboard, and actionable insights for sprint reviews.

Quick Start

Run /retro to generate the latest weekly retro using the default 7-day window.

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

To generate an engineering retrospective from git history, you can run a command that analyzes a specified time window of commits to produce a comprehensive team-wide narrative with per-author metrics, praise, and growth opportunities.

What is a git commit analysis retrospective for software teams?▼

A git commit analysis retrospective is an automated review of team coding activity that extracts metrics like commits, lines of code, and tests to highlight individual contributions and focus patterns for sprint reviews.

Can I analyze git metrics for specific time windows other than weekly?▼

Yes, you can analyze git metrics for specific time windows other than the default weekly retrospective by providing a custom time window parameter to evaluate your team's engineering activity and focus patterns.

How do I get per-person praise and growth recommendations from commit data?▼

You can get per-person praise and growth recommendations from commit data by analyzing individual author metrics such as commit frequency, lines of code, and test contributions within the selected git history window.

What is the best way to prepare a CTO-level engineering metrics report?▼

The best way to prepare a CTO-level engineering metrics report is to aggregate git history into a data-driven summary featuring a team-wide narrative, per-author contributions, a leaderboard, and actionable insights for executive review.

Does the weekly git retrospective include a team leaderboard and focus patterns?▼

Yes, the weekly git retrospective includes a team leaderboard and per-author focus patterns by analyzing commit history to identify activity trends, lines of code written, and test contributions for the specified period.

Related Skills

Explore More Software Engineering Skills→
GenEducationGenEducation

retro

Analyze git commit history to generate weekly engineering retrospectives.

Official
Advanced
89jobrien89jobrien
4

agile-ceremonies

Structure Agile standups, retrospectives, and sprint tracking with action items.

Community
Intermediate
XantibodyXantibody
1

verify

Run static analysis, tests, and formatting sequentially to verify code quality.

Community
Intermediate
yocxy2yocxy2

gstack-openclaw-retro

Analyze git commit history to generate engineering retrospectives.

Community
Advanced