engineering-retro

engineering-retro is a skill for Claude Code from Mathews-Tom/armory. It costs 63 tokens per session (2,351 once invoked), scanned A, original, MIT.

A read-only engineering retrospective based on Git commits and pull requests over a selected time period. A monorepo is one repository containing multiple projects or services, which this can analyze by folder.

In plain words
What is it for?
Use it for 24-hour, 7-day, 14-day, or 30-day reviews, optionally limited to a monorepo area such as services/api.
Why use it?
It shows what the team shipped and how work progressed without changing the codebase.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the armory plugin — 98 skills shipped together

Good fit Use it for 24-hour, 7-day, 14-day, or 30-day reviews, optionally limited to a monorepo area such as services/api.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mathews-tom/armory/engineering-retro
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.

Any agent
npx skills add Mathews-Tom/armory --skill engineering-retro
Clone the repo
git clone --depth 1 https://github.com/Mathews-Tom/armory

Made for: Claude Code.

Or install armory, the plugin that ships this one along with the rest of its 98 skills.

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 engineering-retro

README.md
[![agentmods](https://agentmods.dev/badge/skills/mathews-tom/armory/engineering-retro/github.svg)](https://agentmods.dev/skills/mathews-tom/armory/engineering-retro)
Your own site
<a href="https://agentmods.dev/skills/mathews-tom/armory/engineering-retro"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/engineering-retro/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for engineering-retro

Your own site · 80×15
<a href="https://agentmods.dev/skills/mathews-tom/armory/engineering-retro"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/engineering-retro.svg" alt="Reviewed on agentmods" width="80" 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 2,351 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00063 $0.02351
Opus 5.5 $0.00025 $0.00940
Sonnet 5.5 $0.00013 $0.00470
Haiku 4.5 $0.00006 $0.00235

Measured 1mo ago against content hash 5fb7221d79a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

engineering-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 1mo 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.

skills/engineering-retro/SKILL.md · 297 lines

How it starts

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

Engineering Retrospective

Generate a structured, git-based engineering retrospective for a configurable time window. This is a read-only analysis — no files are modified except the optional JSON snapshot.

Arguments

/engineering-retro [TIME_WINDOW] [PATH_SCOPE]
  • TIME_WINDOW (optional): 24h, 7d (default), 14d, 30d
  • PATH_SCOPE (optional): restrict analysis to a subdirectory (monorepo support), e.g. services/api

Examples:

  • /engineering-retro — last 7 days, full repo
  • /engineering-retro 30d — last 30 days, full repo
  • /engineering-retro 14d services/api — last 14 days, scoped to services/api/

Execution Steps

Step 1: Environment Detection

Detect runtime context before any analysis:

# Default branch
DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
if [ -z "$DEFAULT_BRANCH" ]; then
  DEFAULT_BRANCH=$(git remote show origin 2>/dev/null | grep 'HEAD branch' | awk '{print $NF}')
fi

# System timezone
TZ_NAME=$(date +%Z)

# Time window — convert argument to --since format
# 24h → "24 hours ago", 7d → "7 days ago", 14d → "14 days ago", 30d → "30 days ago"

If DEFAULT_BRANCH detection fails, abort with an error — do not guess.

Step 2: Gather Raw Git Data

Collect commits within the time window on the detected default branch:

# All commits in window (with optional path scope)
git log origin/$DEFAULT_BRANCH --since="$SINCE" --format="%H|%aI|%aN|%s" -- $PATH_SCOPE

# Diff stats for the window
git log origin/$DEFAULT_BRANCH --since="$SINCE" --numstat --format="%H" -- $PATH_SCOPE

Capture: commit hash, author date (ISO), author name, subject line, files changed, insertions, deletions.

Step 3: Compute Aggregate Metrics

From the raw data, compute:

  • Total commits in window
  • Unique contributors (distinct author names)
  • Files changed (unique file paths across all commits)
  • Lines added (sum of insertions)
  • Lines removed (sum of deletions)
  • Net delta (added - removed)
  • Avg commit size (total lines changed / total commits)

Read the full file on GitHub · 297 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago First seen · 297 lines · 63 tokens per session scan A 5fb7221d79a2

Subscribe to this mod's changes

engineering-retro is a skill published in the GitHub repository Mathews-Tom/armory (337 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 2,351 once invoked, about $0.0003 per session on Opus 5.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-30.

Related

Other skills, from other repositories

gh-issues

Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers: gh commands, bulk operations, JSON/jq…

serejaris/personal-corp-os · 104 tokens

gh-pr-review

Review GitHub Pull Requests using the gh CLI. Use when a user asks to review a PR, perform code review, check a pull request, or provide feedback on proposed changes. Triggers on phrases like "review PR", "review pull request", "check PR", "code review".

tao12345666333/ankaloop · 62 tokens

safe-public-release

Use when publishing, open-sourcing, exporting, sanitizing, or moving code, agent skills, prompts, templates, fixtures, datasets, workshop assets, or other artifacts from a private repository, vendor/runtime environment, or mixed working directory into a public repository or registry. Builds a provenance inventory…

serejaris/personal-corp-os · 166 tokens

mx-pr

Draft a pull request from the feature spec and git log, then publish to GitHub or GitLab (Bitbucket experimental) — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name].

maxence2997/mx-harness · 57 tokens

mx-commit

Commit all pending changes as one commit per logical concern, following the project's message convention (type prefix, 50-char subject, English). Use when the working tree may hold several changes or the convention must be enforced; a single trivial change can use plain git commit. Usage: /mx-commit [--auto].

maxence2997/mx-harness · 67 tokens

dirty-worktree-discipline

Keeps agent work safe in messy repositories. Use when git status is dirty, unrelated files exist, generated artefacts are present, multiple agents share a repo, or you must commit only the intended slice without damaging someone else's work.

joelbrilliant/agentic-delivery-skills · 52 tokens