skills.rest
jm199seo
jm199seoCOMMUNITY
Explore all skills by this author →
GitHub

retro

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

Updated Mar 22, 2026
Search Tags:#git#analytics#engineering#telemetry#team#retro
One-click install
npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill retro-jm199seo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/jm199seo/lostark-accessory-viewer/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill retro-jm199seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives can be time-consuming and error-prone. This Skill automates analysis of commit history, team contributions, and code-quality signals to produce a structured, team-aware retrospective with persistent history and growth opportunities.

Core Features & Use Cases

  • Analyze the last window of activity from origin/<default>, identify the current user and summarize per-person contributions with praise and growth opportunities.
  • Maintain a persistent retro history, compute trends, and support side-by-side comparisons across windows.
  • Provide operator-friendly instructions to run /retro with various time windows and comparison modes, plus optional telemetry and contributor-mode workflows.

Quick Start

Run /retro to generate a weekly retrospective for 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 automate weekly engineering retrospectives from git commit history?▼

You can automate weekly engineering retrospectives by analyzing git commit history and per-author contributions from origin/<default> to generate a structured team-wide retrospective with praise, growth opportunities, and persistent history.

Can I generate a team-wide retrospective for a custom time range instead of 7 days?▼

Yes, team-wide retrospectives support custom time ranges alongside the standard 7-day window, allowing you to analyze specific periods of engineering activity from your git history.

Does the automated retrospective analysis track individual developer contributions?▼

Automated retrospective analysis tracks individual developer contributions by identifying per-author commits, generating personalized praise, and highlighting specific growth opportunities for each team member.

How do I compare engineering activity trends across different retrospective periods?▼

You can compare engineering activity trends by maintaining persistent retro history stored under .context/retros, enabling side-by-side comparisons and trend computation across multiple analysis windows.

What is contributor-mode in engineering telemetry analysis?▼

Contributor-mode in engineering telemetry analysis is an optional workflow control that adjusts how per-author contributions and commit histories are evaluated during the retrospective generation process.

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
GTC6244GTC6244

retro

Analyze commit history and code quality metrics to generate weekly team retrospectives.

Community
Advanced
2460124601

retro

Generate weekly or cross-project engineering retrospectives from git history and contributor activity.

Community
Advanced
nocnocgroupnocnocgroup

retro

Aggregate commits, PRs, and test activity into team retrospectives.

Official
Advanced