pull-request SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
pull-request from ddd-ts-kit/ddd-ts-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ddd-ts-kit/ddd-ts-kit/pull-request@git:20261030.ebb9071Pins git:20261030.ebb9071 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ddd-ts-kit/ddd-ts-kit
- Path
plugin/skills/pull-request/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261030.ebb9071, committed Oct 30, 2026
- First version recorded
- Oct 23, 2026
- Size
- 4,482 bytes
- Repository stars
- 24
- License
- MIT
Takes the pull request of a story to green: failing checks, then each unresolved review comment under the rules of the story, never force-pushed, until only the code owner is waited on. Run by the user with /ddd-ts-kit:pull-request <number>.
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
# Take a pull request to green Pull request: `$ARGUMENTS` You work in the worktree of the story the pull request comes from (`.ddd-ts-kit/story.json` names it; `npx ddd-ts-kit story` says where it stands), under the rules of the story skill: the guard, the locked acceptance, the decisions of the story file. You change the branch only, never the trunk, and never with a force-push: the history the reviewers read stays. Reading costs: [../start/token-economy.md](../start/token-economy.md). ## The loop 1. Read what waits, in one pass: `gh pr view $ARGUMENTS --json url,state,reviewDecision, mergeStateStatus,statusCheckRollup`, the unresolved review threads (`gh api graphql` on the `reviewThreads` of the pull request, those with `isResolved: false`, each with its path, its line and its comments) and the failing checks (`gh pr checks $ARGUMENTS`). On GitLab: `glab mr view $ARGUMENTS --comments` and the pipeline of the branch. 2. Address each item, checks first (a red check is often what a comment is about), then the threads, oldest first: - a failing check: read its log, fix the cause in the code, never in the check, the threshold …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5b525wcanarxdmnr/8518e94c3c53b1517f48387c49b7f596b55cd6514c50e396d70506f9ae9943bb.json
Then /plugin install pull-request@markdownregistry-5b525wcanarxdmnr in Claude Code. It installs git:20261030.ebb9071, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add ddd-ts-kit/ddd-ts-kit/pull-request@sha256:8518e94c3c53b151The line at the top of this page pins the label git:20261030.ebb9071, 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_5b525wcanarxdmnr)
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 ddd-ts-kit/ddd-ts-kit/pull-request 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 pull-request from somewhere else? Ask it: where did my pull-request 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 3 versions of this file, between Oct 23, 2026 and Oct 30, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261030.ebb9071 latest | 2026-10-30 | ebb9071 | 4,482 B | A | view · diff |
| git:20261029.b929ced | 2026-10-29 | b929ced | 3,889 B | A | view · diff |
| git:20261023.69338b2 | 2026-10-23 | 69338b2 | 4,280 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/pull-request/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 (4482 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
ddd-ts-kit/ddd-ts-kit · 24 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5b525wcanarxdmnr GET https://markdownregistry.com/api/v1/resolve?ref=ddd-ts-kit/ddd-ts-kit/pull-request GET https://markdownregistry.com/api/v1/blob/8518e94c3c53b1517f48387c49b7f596b55cd6514c50e396d70506f9ae9943bb
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.
More from ddd-ts-kit/ddd-ts-kit
Every file in ddd-ts-kit/ddd-ts-kit