A command that examines recent Git history and produces a retrospective, which is a review of what went well, what could improve, and what actions to take.

Use it to review a day, week, sprint, or custom date range, including commits, changed files, code churn, test additions, bug-fix ratios, and available pull-request metrics.

It turns commit history into a structured view of development patterns instead of relying only on memory.

retro — Command for coding agents by Claude-Code-Community-Ireland: A command that examines recent Git history and produces…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/claude-code-community-ireland/claude-code-resources/retro

Clone the repo

git clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resources

Or install vibeworks-library, the plugin that ships this one along with the rest of its 34 skills, 21 commands, 34 agents, 3 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/claude-code-community-ireland/claude-code-resources/retro.svg)](https://agentmods.dev/commands/claude-code-community-ireland/claude-code-resources/retro)

Your own site

<a href="https://agentmods.dev/commands/claude-code-community-ireland/claude-code-resources/retro"><img src="https://agentmods.dev/badge/commands/claude-code-community-ireland/claude-code-resources/retro.svg" alt="Measured on agentmods" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 528 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00017	$0.00528
Opus 5	$0.00009	$0.00264
Sonnet 5	$0.00003	$0.00106
Haiku 4.5	$0.00002	$0.00053

Measured 4d ago against content hash cc84c0402269, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

retro scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/vibeworks-library/commands/retro.md · 64 lines

What it actually says

Retrospective Workflow

You are generating a retrospective analysis of recent development work.

Steps

Determine time period: Read $ARGUMENTS:
- today — Last 24 hours
- this-week (default) — Last 7 days
- this-sprint — Last 14 days
- Or a specific date range

Gather data: Analyze the git history for the period:

git log --since="<period>" --oneline --stat
git log --since="<period>" --format="%h %s" --no-merges
git shortlog --since="<period>" -sn

Analyze patterns:
- Commit types: Count feat, fix, refactor, test, docs, chore commits
- Hotspots: Files changed most frequently (potential complexity/instability)
- Churn: Files with many additions AND deletions (rework indicator)
- Test coverage changes: New test files added vs source files added
- Bug fix ratio: Fixes vs features (high fix ratio = quality issues)
- PR metrics: If available, check average PR size and review time

Generate the retrospective:

## Retrospective: [period]

### Summary
X commits, Y files changed, Z lines added, W lines removed

### What Went Well
- [Completed features, good patterns observed, test improvements]

### What Could Improve
- [Recurring bug patterns, high-churn files, missing tests, tech debt]

### Metrics
| Metric | Value |
|--------|-------|
| Features added | X |
| Bugs fixed | Y |
| Tests added | Z |
| Hotspot files | [list] |
| Fix/feature ratio | X:Y |

### Action Items
- [ ] [Specific, actionable improvement with owner]
- [ ] [Specific, actionable improvement with owner]
- [ ] [Specific, actionable improvement with owner]

Present: Show the retrospective and highlight the top 3 action items.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

4d ago First seen · 64 lines · 17 tokens per session scan A cc84c0402269

Subscribe to this mod's changes

retro is a command published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (10 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 528 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Project management

retro

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Retrospective Workflow

Steps

What this file has done since we first saw it

Other commands, from other repositories

template

sync-linear

add-note

fest-show

dispatcher

clarify