engineering-retro SKILL.md skillA
engineering-retro from mathews-tom/armory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mathews-tom/armory/engineering-retro@v1.0.1Pins v1.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mathews-tom/armory
- Path
skills/engineering-retro/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.1, committed Apr 11, 2026
- First version recorded
- Mar 26, 2026
- Size
- 9,187 bytes
- Repository stars
- 334
- License
- MIT
Git-based engineering retrospective analyzing commits, PRs, and velocity over configurable windows with monorepo path scoping. Triggers on: "retrospective", "sprint retro", "weekly review", "what did we ship", "engineering retro", "dev summary", "commit analysis".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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:
```bash
# 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"
```
…Read the whole file at its exact version.
How to install
mdr add mathews-tom/armory/engineering-retro@sha256:5fb7221d79a2797fThe line at the top of this page pins the label v1.0.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_44yqja4vbbterijv)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 26, 2026 and Apr 11, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-04-11 | 0aa221a | 9,187 B | A | view · diff |
| v1.0.1 | 2026-04-09 | 1cc63e5 | 9,451 B | B | view · diff |
| v1.0.1 | 2026-04-07 | b03849d | 9,437 B | B | view · diff |
| v1.0.0 | 2026-03-27 | d46cf2e | 9,437 B | B | view · diff |
| v1.0.0 | 2026-03-26 | 6fe71e6 | 9,198 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9187 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mathews-tom/armory · 334 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_44yqja4vbbterijv GET https://markdownregistry.com/api/v1/resolve?ref=mathews-tom/armory/engineering-retro GET https://markdownregistry.com/api/v1/blob/5fb7221d79a2797f19bab0e99c4f9f1b58863be6c0959528c03158f767126e83
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.