pr-implement SKILL.md skillA
pr-implement from motleyai/living-architecture is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add motleyai/living-architecture/pr-implement@git:20261113.d986ed8Pins git:20261113.d986ed8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- motleyai/living-architecture
- Path
plugin/skills/pr-implement/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261113.d986ed8, committed Nov 13, 2026
- First version recorded
- Nov 9, 2026
- Size
- 7,565 bytes
- Repository stars
- 14
- License
- MIT
Stage 3 of 4 of the /la:pr flow — implement until every test from the pr-tests stage passes, then commit, push and, with the user's explicit go-ahead, open the PR. Normally dispatched by /la:pr; if the /la:pr context (BRANCH, CHANGE_ID, OPENSPEC, tracker issue) is not already loaded in this session, invoke the la:pr skill instead.
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
**Stage 3 of 4 of the `/la:pr` flow.** Prerequisite: `/la:pr` has run in this session, preflight included, and established `BRANCH`, `CHANGE_ID`, `OPENSPEC`, and the full tracker issue (body + comments), if there is one. If any of that is missing, invoke the `la:pr` skill instead — it rehydrates and dispatches back here. The `/la:pr` stopping policy applies throughout this stage. Before writing anything, recover the durable plan (the `openspec/changes/<CHANGE_ID>/` folder when `OPENSPEC=1`, else the plan comment on the tracker issue) and the failing tests already on disk from `pr-tests`. ## Step 1 — Implement until tests pass Implement the plan. After changes, run the tests in the `/la:pr` local test scope and fix any failures. Do not declare done until every test from the `pr-tests` stage passes. An existing test that breaks because it pins what the plan changes is not a design fork: ask only for approval to align it with the plan (the `/la:pr` stopping policy), never with alternative options. **Symptom vs. structural cause — decide before you patch.** The plan already chose between a band-aid and a structural fix; implement the structural shape …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_35yzwbayj6uvr6nr/91021ada6f61d3f9aef8cff47a8256a0f301e29ce859d911a93328200d085a37.json
Then /plugin install pr-implement@markdownregistry-35yzwbayj6uvr6nr in Claude Code. It installs git:20261113.d986ed8, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add motleyai/living-architecture/pr-implement@sha256:91021ada6f61d3f9The line at the top of this page pins the label git:20261113.d986ed8, 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_35yzwbayj6uvr6nr)
1 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 motleyai/living-architecture/pr-implement 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 pr-implement from somewhere else? Ask it: where did my pr-implement 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 9, 2026 and Nov 13, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.d986ed8 latest | 2026-11-13 | d986ed8 | 7,565 B | A | view · diff |
| git:20261112.24061e6 | 2026-11-12 | 24061e6 | 8,116 B | A | view · diff |
| git:20261112.d9c676d | 2026-11-12 | d9c676d | 8,124 B | A | view · diff |
| git:20261111.743f923 | 2026-11-11 | 743f923 | 7,942 B | A | view · diff |
| git:20261109.20ba352 | 2026-11-09 | 20ba352 | 7,950 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/pr-implement/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 (7565 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
motleyai/living-architecture · 14 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_35yzwbayj6uvr6nr GET https://markdownregistry.com/api/v1/resolve?ref=motleyai/living-architecture/pr-implement GET https://markdownregistry.com/api/v1/blob/91021ada6f61d3f9aef8cff47a8256a0f301e29ce859d911a93328200d085a37
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.