skills.rest
Simon-YHKim
Simon-YHKimCOMMUNITY
Explore all skills by this author →
GitHub

retro

Generates weekly engineering retrospectives from git commit history with per-contributor metrics and trend tracking.

Updated Apr 5, 2026
Search Tags:#retrospective#engineering metrics#commit analysis#sprint review#team productivity#trend tracking#git analytics
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill retro-simon-yhkim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill retro-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Engineering teams and solo developers lack visibility into how they actually work: when they code, what they ship, whether test coverage is improving, and how each contributor is performing. This Skill turns raw git history into a structured retrospective with metrics, trends, and actionable feedback. ## Core Features & Use Cases - Commit & Velocity Analysis: Parses git log to compute commits, LOC, PR sizes, commit-type mix (feat/fix/refactor), and hotspot files over configurable windows (24h, 7d, 14d, 30d). - Team-Aware Breakdown: Identifies each contributor, reports per-person commits, focus areas, test ratios, and session patterns, with specific praise and growth suggestions anchored in real commits. - Persistent Trend Tracking: Saves JSON snapshots to .context/retros/ and compares against prior retros to show week-over-week deltas in test ratio, fix ratio, sessions, and shipping streaks. - Use Case: At the end of a sprint, run the retro to get a tweetable summary, a per-author leaderboard, session pattern analysis, and a trends table showing whether code quality is improving. ## Quick Start Ask the assistant to run a weekly engineering retrospective over the last 7 days of git history on the main branch.

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

Run the retro skill with a time window argument such as 7d, 14d, or 30d. It parses git log on the default branch to compute commits, LOC, test ratios, session patterns, and per-author breakdowns, then writes a structured narrative report.

How to track code quality trends across sprints?▼

The skill saves each retro as a JSON snapshot in .context/retros/ and loads the most recent prior snapshot on the next run. It then computes deltas for test ratio, fix ratio, sessions, and LOC per hour so trends are visible week over week.

Can I compare this week's activity against the previous period?▼

Yes, use the compare argument with an optional window, such as compare 14d. The skill analyzes the current window and the prior same-length window side by side instead of producing a single-period report.

Does the retro work for teams with multiple contributors?▼

Yes, it identifies the current user via git config and treats all other authors as teammates. Each contributor gets commits, LOC, focus areas, session patterns, test discipline, plus specific praise and one growth suggestion anchored in actual commits.

What time windows does the retrospective support?▼

Supported windows are hours (24h), days (7d, 14d, 30d), and weeks (2w). Day and week windows align to local midnight for accurate boundaries. There is also a global mode for cross-project retros that does not require a git repository.

Why does the retro show no trend comparison on first run?▼

Trend comparison requires at least one prior snapshot in .context/retros/. On the first run no history exists, so the skill saves the current snapshot and notes that trends will appear starting with the next retro.

Related Skills

Explore More Software Engineering Skills→
showcase-gig-platformshowcase-gig-platform
4

create-pr

Create GitHub pull requests with conventional commit titles and detailed bodies.

Official
Advanced
ComputerConnectionComputerConnection

sprint-retro

Collect sprint phase data and generate a Sprint Retro document.

Community
Advanced
abdulazeezojabdulazeezoj

retro

Analyzes commit history and code metrics to generate weekly engineering retrospectives.

Community
Advanced
githubgithub
38.5k

repo-story-time

Generates repository summaries and narrative stories from git commit history analysis.

Official
Intermediate