archify-pr SKILL.md skillA
archify-pr from tt-a1i/archify is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tt-a1i/archify/archify-pr@v3.3Pins v3.3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tt-a1i/archify
- Path
archify-pr/SKILL.md- Versions recorded
- 5
- Latest version
- v3.3, committed Nov 22, 2026
- First version recorded
- Nov 17, 2026
- Size
- 6,680 bytes
- Repository stars
- 98,762
- License
- Apache-2.0
Explain git branch changes, diffs, and GitHub pull requests or GitLab merge requests with visual architecture, workflow, sequence, ERD, or lifecycle walkthroughs. When a pull request carries material architectural, flow, schema, or async-state changes, lightly offer optional Archify PR diagrams and their review benefit without forcing them; build and attach Camo-safe dual-theme story or static diagrams when the user agrees or explicitly asks. Requires the companion archify core Skill.
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
# Archify PR Turn a branch change or pull request into diagrams that show what changed, where it propagates, and with what neighbours. Read the code as the authority; report evidence, never a risk verdict. Every command goes through this Skill's wrapper, `bin/archify-pr.mjs`: ```bash node <archify-pr-root>/bin/archify-pr.mjs pr validate <manifest.json> --repo-root <repo> --json ``` The wrapper delegates unchanged to the installed core `archify/bin/archify.mjs`. It never downloads or installs anything. ## Route the request ### Explicit PR visualization When the user asks to explain or visualize a PR, a branch change, or a `git diff`, or to run `archify pr`, start the workflow directly. Read [`references/pr-workflow.md`](references/pr-workflow.md), pin the three-dot range from `git merge-base`, and build the pack; do not ask whether a diagram is wanted. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gz64ox5mnpmjccoa/0b5dd9b781a27d8d2d342c6b4239104d75bfeb4f27fc8c3b677a264b0198ee97.json
Then /plugin install archify-pr@markdownregistry-gz64ox5mnpmjccoa in Claude Code. It installs v3.3, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add tt-a1i/archify/archify-pr@sha256:0b5dd9b781a27d8dThe line at the top of this page pins the label v3.3, 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_gz64ox5mnpmjccoa)
0 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 tt-a1i/archify/archify-pr 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 archify-pr from somewhere else? Ask it: where did my archify-pr 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 Nov 17, 2026 and Nov 22, 2026, about one every day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v3.3 latest | 2026-11-22 | 7a3dc70 | 6,680 B | A | view · diff |
| v3.2 | 2026-11-18 | db62406 | 6,680 B | A | view · diff |
| v3.2 | 2026-11-18 | b586be3 | 6,497 B | A | view · diff |
| v3.2 | 2026-11-18 | ca0928a | 6,297 B | A | view · diff |
| v3.2 | 2026-11-17 | 2186c68 | 5,615 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/archify-pr/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 (6680 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
tt-a1i/archify · 98,762 stars · license Apache-2.0 · pushed 2026-11-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gz64ox5mnpmjccoa GET https://markdownregistry.com/api/v1/resolve?ref=tt-a1i/archify/archify-pr GET https://markdownregistry.com/api/v1/blob/0b5dd9b781a27d8d2d342c6b4239104d75bfeb4f27fc8c3b677a264b0198ee97
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.