retro

retro is a skill for Claude Code, Codex from HECer/yoke. It costs 63 tokens per session (3,798 once invoked), scanned A, original, MIT.

A command for reviewing recent software-development work by analyzing commit history, work patterns, and code-quality measures. It can identify contributors and provide individual feedback for a chosen time period.

In plain words
What is it for?
Producing 24-hour, weekly, 14-day, or 30-day engineering retrospectives, comparing periods, and summarizing each contributor's strengths and growth areas.
Why use it?
It turns repository history into a structured review of what happened, where work can improve, and how the current period compares with an earlier one.

Skill for Claude CodeCodex

Part of the yoke plugin — 34 skills, 1 hook shipped together

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 skills/hecer/yoke/retro
Any agent
npx skills add HECer/yoke --skill retro
Clone the repo
git clone --depth 1 https://github.com/HECer/yoke

Made for: Claude Code, Codex.

Or install yoke, the plugin that ships this one along with the rest of its 34 skills, 1 hook.

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.

agentmods badge for retro

README.md
[![agentmods](https://agentmods.dev/badge/skills/hecer/yoke/retro.svg)](https://agentmods.dev/skills/hecer/yoke/retro)
Your own site
<a href="https://agentmods.dev/skills/hecer/yoke/retro"><img src="https://agentmods.dev/badge/skills/hecer/yoke/retro.svg" alt="Measured on agentmods" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,798 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.

ModelPer sessionOnce invoked
Fable 5 $0.00063 $0.03798
Opus 5 $0.00032 $0.01899
Sonnet 5 $0.00013 $0.00760
Haiku 4.5 $0.00006 $0.00380

Measured 4d ago against content hash f8ca5bd1cdce, 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.

canon/skills/retro/SKILL.md · 398 lines

How it starts

The opening of the file, as written. The whole thing — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Engineering Retrospective

You are running the retro skill. Generate a comprehensive engineering retrospective analyzing commit history, work patterns, and code quality metrics.

Arguments

  • (none) — default: last 7 days
  • 24h — last 24 hours
  • 14d — last 14 days
  • 30d — last 30 days
  • compare — compare current window vs prior same-length window
  • compare 14d — compare with explicit window

Instructions

Parse the argument to determine the time window. Default to 7 days if no argument given. All times should be reported in the user's local timezone (use the system default — do NOT set TZ).

Midnight-aligned windows: For day (d) and week (w) units, compute an absolute start date at local midnight, not a relative string. For example, if today is 2026-03-18 and the window is 7 days: the start date is 2026-03-11. Use --since="2026-03-11T00:00:00" for git log queries — the explicit T00:00:00 suffix ensures git starts from midnight. For week units, multiply by 7 to get days. For hour (h) units, use --since="N hours ago".

Argument validation: If the argument doesn't match a number followed by d, h, or w, or the word compare (optionally followed by a window), show usage and stop:

Usage: retro [window | compare]
  retro              — last 7 days (default)
  retro 24h          — last 24 hours
  retro 14d          — last 14 days
  retro 30d          — last 30 days
  retro compare      — compare this period vs prior period
  retro compare 14d  — compare with explicit window

Step 1: Gather Raw Data

First, fetch origin and identify the current user:

git fetch origin <default> --quiet
git config user.name
git config user.email

The name returned by git config user.name is "you" — the person reading this retro. All other authors are teammates.

Run ALL of these git commands in parallel (they are independent):

# 1. All commits in window with timestamps, subject, hash, author, files changed
git log origin/<default> --since="<window>" --format="%H|%aN|%ae|%ai|%s" --shortstat

# 2. Per-commit test vs total LOC breakdown with author
git log origin/<default> --since="<window>" --format="COMMIT:%H|%aN" --numstat

# 3. Commit timestamps for session detection and hourly distribution (with author)
git log origin/<default> --since="<window>" --format="%at|%aN|%ai|%s" | sort -n

# 4. Files most frequently changed (hotspot analysis)
git log origin/<default> --since="<window>" --format="" --name-only | grep -v '^$' | sort | uniq -c | sort -rn

# 5. PR/MR numbers from commit messages (GitHub #NNN, GitLab !NNN)
git log origin/<default> --since="<window>" --format="%s" | grep -oE '[#!][0-9]+' | sort | uniq

# 6. Per-author file hotspots (who touches what)
git log origin/<default> --since="<window>" --format="AUTHOR:%aN" --name-only

# 7. Per-author commit counts (quick summary)
git shortlog origin/<default> --since="<window>" -sn --no-merges

# 8. TODOS.md backlog (if available)
cat TODOS.md 2>/dev/null || true

# 9. Test file count
find . -name '*.test.*' -o -name '*.spec.*' -o -name '*_test.*' -o -name '*_spec.*' 2>/dev/null | grep -v node_modules | wc -l

# 10. Regression test commits in window
git log origin/<default> --since="<window>" --oneline --grep="test:" --grep="regression"

# 11. Test files changed in window
git log origin/<default> --since="<window>" --format="" --name-only | grep -E '\.(test|spec)\.' | sort -u | wc -l

Read the full file on GitHub · 398 lines

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.

  1. 4d ago First seen · 398 lines · 63 tokens per session scan A f8ca5bd1cdce

Subscribe to this mod's changes

retro is a skill published in the GitHub repository HECer/yoke (2 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 3,798 once invoked, about $0.0003 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.