retro

/retro — Engineering Retrospective Workflow

Data-driven retrospective from git history. Analyzes commits, contributors, and trends. Produces actionable reports.

Usage

/retro              — Last 7 days
/retro --days 14    — Last 14 days
/retro --since 2024-01-01 --until 2024-01-31  — Custom range
/retro --save       — Save JSON snapshot for trend tracking

Procedure

1. Gather Data

Run git commands to collect commits, authors, file changes, and timestamps for the specified period.

2. Compute Metrics

• Commits (total + per-contributor)
• LOC added/removed, net change
• Test ratio (commits touching test files vs. total)
• Fix ratio (commits with "fix"/"bug" in message vs. total)
• Peak activity hours
• Biggest ship (largest change by scope)

3. Analyze Patterns

• Work focus distribution (features, fixes, refactoring, infra)
• Shipping cadence (regular vs. batched)
• Test-to-feature code ratio trends
• Contributor patterns

4. Produce Report

Use the template at templates/retro-report.md for output format.

5. Save Snapshot (optional, with --save)

Save a JSON snapshot for trend comparison across retros.

Scripts

• Windows: scripts/retro.ps1
• Unix: scripts/retro.sh

Agent Instructions

1. Run the retro script for the user's platform to gather raw data.
2. Analyze the data per the procedure above.
3. Produce the report using the template.
4. Always follow .github/agents/retro.agent.md for persona and rules.