skills.rest
TioSavich
TioSavichCOMMUNITY
Explore all skills by this author →
GitHub

retro

Aggregate Git activity into a team-aware retrospective JSON snapshot.

Updated Sep 10, 2024
Search Tags:#git#analysis#metrics#engineering#team#retro
One-click install
npx skills add https://github.com/TioSavich/UMEDCTA --skill retro-tiosavich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/TioSavich/UMEDCTA/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/TioSavich/UMEDCTA --skill retro-tiosavich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that analyze commit history, work patterns, and code quality metrics, delivering team-aware praise and growth opportunities with persistent history.

Core Features & Use Cases

  • Analyze commits, author contributions, file churn, and PR activity to surface team health and focus areas.
  • Generate per-author praise and growth recommendations based on contribution patterns.
  • Produce a structured snapshot saved to .context/retros, with optional data sections (greptile history, backlog, test health) when data exists.

Quick Start

Run the retro for the default 7-day window, or specify a window like 14d to view a longer period.

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

Generate a team-aware engineering retrospective by aggregating Git commits, insertions, deletions, and file churn over a configurable window to produce a structured snapshot of per-author contributions and growth opportunities.

What metrics are analyzed in a Git-based team retrospective?▼

A Git-based team retrospective analyzes commit counts, insertions, deletions, file churn, test proxies, and PR activity to surface engineering work patterns, team health, and focus areas.

Can I run a retrospective for a longer project period instead of a weekly sprint?▼

Yes, you can analyze longer project periods by specifying a custom window like 14d instead of the default 7-day window to aggregate extended Git activity and produce a comprehensive retrospective snapshot.

Does the retrospective analysis require specific Git branch configurations?▼

The retrospective analysis queries the origin/<default> branch and aligns midnight windows to aggregate Git activity, satisfying frontmatter requirements without needing complex custom branch configurations.

Where are the generated retrospective analysis results stored?▼

The generated retrospective analysis results are saved as a persistent JSON snapshot in the .context/retros directory, preserving the engineering team's work patterns and metrics history.

What optional data sections are included in the Git retrospective snapshot?▼

Optional data sections for greptile history, backlog, and test health are included in the retrospective snapshot only when the underlying data exists in the analyzed Git repository.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1

diff-analyze

Analyze git differences and commit history between the current branch and origin main.

Community
Basic
jm199seojm199seo

retro

Analyze commit history and per-author contributions to generate team retrospectives.

Community
Advanced
fghaffarfghaffar

retro

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

Community
Advanced
SeongHuniSeongHuni

retrospective

Generate sprint or milestone retrospectives by analyzing project data.

Community
Intermediate