review-retro SKILL.md skillA
review-retro from alexisbalayre/claude-code-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add alexisbalayre/claude-code-config/review-retro@git:20261017.c5ad833Pins git:20261017.c5ad833 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- alexisbalayre/claude-code-config
- Path
.claude/skills/review-retro/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261017.c5ad833, committed Oct 17, 2026
- First version recorded
- Sep 17, 2026
- Size
- 6,003 bytes
- Repository stars
- 3
- License
- MIT
Mine past automated-review runs for recurring process and judgment failures, then propose fixes to the review setup as one evidence-cited PR. Use when running the review retrospective or tuning the PR reviewer.
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
# Review retro You run the retrospective for the automated review setup (the learn stage of the review pipeline). The review pipeline reviews code; you review the pipeline. Your deliverable is not findings about code: it is improvements to the setup itself, grounded in past runs. **Dormant until there is history.** The retro needs a window of real review runs and the human outcomes on them. Until the merged producer has reviewed a stretch of PRs, there is nothing to mine: say so and stop rather than inventing patterns from a handful of runs. > **Setup:** the `ci/review-metrics` branch is produced by > [`claude-code-review.yml`](../../../.github/workflows/claude-code-review.yml) (which runs > `/pr-ci-review` with a `--json-schema` from [`tools/review`](../../../tools/review/) and > appends each run's record). Until that workflow is enabled and has history, the retro > degrades gracefully — it reports there is no history to mine and stops. ## Evidence Three sources, all reachable through `gh` or `git`: …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_sjrfuc5npmxtqazu/a345757f64ea899c7f320d59723d47cbda5e3c8641e9da1fe2a96b7b3e1b2bde.json
Then /plugin install review-retro@markdownregistry-sjrfuc5npmxtqazu in Claude Code. It installs git:20261017.c5ad833, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add alexisbalayre/claude-code-config/review-retro@sha256:a345757f64ea899cThe line at the top of this page pins the label git:20261017.c5ad833, 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_sjrfuc5npmxtqazu)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in alexisbalayre/claude-code-config/review-retro since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of review-retro from somewhere else? Ask it: where did my review-retro come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Sep 17, 2026 and Oct 17, 2026, about one every 8 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.c5ad833 latest | 2026-10-17 | c5ad833 | 6,003 B | A | view · diff |
| git:20261017.279b6aa | 2026-10-17 | 279b6aa | 5,840 B | A | view · diff |
| git:20261017.1dbd348 | 2026-10-17 | 1dbd348 | 5,571 B | A | view · diff |
| git:20261017.99c76d6 | 2026-10-17 | 99c76d6 | 5,335 B | A | view · diff |
| git:20260917.a589e3f | 2026-09-17 | a589e3f | 5,179 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/review-retro/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (6003 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
alexisbalayre/claude-code-config · 3 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sjrfuc5npmxtqazu GET https://markdownregistry.com/api/v1/resolve?ref=alexisbalayre/claude-code-config/review-retro GET https://markdownregistry.com/api/v1/blob/a345757f64ea899c7f320d59723d47cbda5e3c8641e9da1fe2a96b7b3e1b2bde
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.