review-test SKILL.md skillA
review-test from chrisallenlane/claude-swe-workflows is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chrisallenlane/claude-swe-workflows/review-test@git:20261116.75ffff6Pins git:20261116.75ffff6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chrisallenlane/claude-swe-workflows
- Path
skills/review-test/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261116.75ffff6, committed Nov 16, 2026
- First version recorded
- Oct 30, 2026
- Size
- 23,193 bytes
- Repository stars
- 21
- License
- MIT
Test suite review covering unit, integration, E2E (browser), and fuzz coverage plus test quality. Advisory only; produces findings and proposes tickets, does not change tests.
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
# Test Review — Comprehensive Test Suite Survey Five-phase survey: unit coverage gaps, integration coverage gaps, E2E (browser) coverage gaps when applicable, fuzz coverage gaps, then test quality issues. Each phase runs its analysis and contributes findings to a consolidated report; at the end, the skill proposes a ticket structure for the recommended work and creates tickets after operator approval. **Advisory only.** The skill produces findings and proposes tickets; it does not implement test changes. The cognitive seam between "find a coverage gap" and "design a test for it" is wide enough that mixing them under one workflow degrades both — test design requires fresh reasoning about edge cases, mocking strategy, and assertion shape, and the discovery agents shouldn't be biased toward gaps whose fixes are easy. Tickets capture findings durably across that seam and compose with `/implement` for remediation. The same logic applies in reverse to test-quality findings (DELETE / REWRITE / SIMPLIFY): the operator should approve removing or rewriting an existing test explicitly, via a ticket, rather than have a workflow do it as a side effect of running a review. ## Philosophy …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_hn5z5gyiqov5pgzc/5dfcc4d3e6ed2ca8220609baadf945faa7089dda9015216d5d099b327c4dc827.json
Then /plugin install review-test@markdownregistry-hn5z5gyiqov5pgzc in Claude Code. It installs git:20261116.75ffff6, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add chrisallenlane/claude-swe-workflows/review-test@sha256:5dfcc4d3e6ed2ca8The line at the top of this page pins the label git:20261116.75ffff6, 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_hn5z5gyiqov5pgzc)
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 chrisallenlane/claude-swe-workflows/review-test 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-test from somewhere else? Ask it: where did my review-test 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 Oct 30, 2026 and Nov 16, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261116.75ffff6 latest | 2026-11-16 | 75ffff6 | 23,193 B | A | view · diff |
| git:20261116.e39effb | 2026-11-16 | e39effb | 23,292 B | A | view · diff |
| git:20261116.0b1f268 | 2026-11-16 | 0b1f268 | 30,989 B | A | view · diff |
| git:20261116.bf4eac1 | 2026-11-16 | bf4eac1 | 30,858 B | A | view · diff |
| git:20261030.96bb2f2 | 2026-10-30 | 96bb2f2 | 30,836 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-test/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 (23193 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
chrisallenlane/claude-swe-workflows · 21 stars · license MIT · pushed 2026-11-17 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_hn5z5gyiqov5pgzc GET https://markdownregistry.com/api/v1/resolve?ref=chrisallenlane/claude-swe-workflows/review-test GET https://markdownregistry.com/api/v1/blob/5dfcc4d3e6ed2ca8220609baadf945faa7089dda9015216d5d099b327c4dc827
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.