rune-retro

Analyzes git commit history to generate engineering retrospectives with per-person breakdowns and trend tracking.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-retro-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-retro
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-retro
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-retro-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams ship code every week but rarely pause to examine how they work. This Skill turns raw git history into an actionable engineering retrospective, surfacing work patterns, code quality signals, and concrete improvement habits without manual data gathering. ## Core Features & Use Cases - Automated Metrics: Computes commits, LOC, test ratio, fix ratio, session depth, and shipping streaks directly from git history for any time window (24h, 7d, 14d, 30d). - Per-Person Breakdowns: Gives each contributor specific praise anchored in real commits plus one constructive growth opportunity, with the deepest analysis for the current user. - Trend & Milestone Tracking: Saves JSON snapshots to .rune/retros/ for period-over-period comparison and triggers deeper milestone analyses at the 1-month, quarter, half-year, and year marks. - Use Case: Run /rune retro 14d at the end of a sprint to get a narrative report covering velocity, churn hotspots without test coverage, focus score, top 3 wins, and 3 habits for the next sprint. ## Quick Start Ask the AI to run a retro on the last 7 days of git history and produce the engineering retrospective report.

Frequently Asked Questions about rune-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?

Invoke the retro command with a time window such as 7d, 14d, or 30d. The skill runs git log queries to compute commits, LOC, test ratio, fix ratio, and sessions, then writes a narrative report with wins, improvements, and habits.

What metrics does a git-based sprint retro track?

It tracks commits, contributors, lines added and removed, test LOC ratio, fix ratio, active days, session depth via a 45-minute gap threshold, churn hotspots, focus score, and shipping streaks for both team and individual.

Does the retro skill modify my code or repository?

No. The skill is strictly read-only: it analyzes git history and writes only its own output artifacts, JSON snapshots and reports, into the .rune/retros/ directory. It never changes source files or creates PRs.

How does retro trend tracking work across multiple weeks?

Each run saves a JSON snapshot to .rune/retros/. On subsequent runs, the skill reads prior snapshots and computes deltas for metrics like test ratio and fix ratio, and deeper milestone analyses trigger at 4, 12, 24, and 50 retros.

What happens when there are no commits in the retro window?

The skill detects empty windows early and reports that there is nothing to retro for the selected period, rather than producing a misleading report with zeroed metrics.