check-merge SKILL.md skillB
check-merge from vzakharov/muthur is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vzakharov/muthur/check-merge@git:20261027.34a00c5Pins git:20261027.34a00c5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vzakharov/muthur
- Path
.claude/skills/check-merge/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261027.34a00c5, committed Oct 27, 2026
- First version recorded
- Sep 30, 2026
- Size
- 7,925 bytes
- Repository stars
- 22
- License
- MIT
Check once whether the branch's merge target (the branch its PR is based on) advanced or the PR landed since the branch was last attested, then hand any advance back to the enclosing flow to decide. While the PR is open, also reconcile the `Proposed squash body:` comment `/finalize` left on it, and the PR title it lands under — editing both in place when the branch has drifted from them. A manual one-shot — run it when you return to a session whose branch is attested to see if the merge target…
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
**Optional branch/PR target**: if the first token of the argument is a branch name, `#NNN` PR number, or PR URL, then `/check-merge <target>` is shorthand for attaching to that branch first and then checking — equivalent to `/from-branch <target> check-merge`. Load `@.claude/skills/from-branch/SKILL.md` and follow it to attach to `<target>`, then run the check below. With no argument, check the current branch as usual. Check **once** whether the branch's **merge target** has moved out from under the branch, or whether the PR landed. The merge target is the branch the open PR is **based on** — resolved from the PR, not hardcoded to `main` — so this stays correct for a PR based on a promotion branch or a long-lived feature branch. With no PR it falls back to the repo default branch. Once the branch is attested the enclosing flow **ends its turn** (so the session reads as **idle**, not pinned as "working"); when the operator returns and runs `/check-merge`, this performs a single check and reports. This is the last check before the code lands: nothing runs at merge time, so a base that moved out from under an …
Read the whole file at its exact version.
How to install
mdr add vzakharov/muthur/check-merge@sha256:7f4ab8793922a818The line at the top of this page pins the label git:20261027.34a00c5, 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_hmjka2qyjtcyr6iu)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 30, 2026 and Oct 27, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.34a00c5 latest | 2026-10-27 | 34a00c5 | 7,925 B | B | view · diff |
| git:20261015.29efa2d | 2026-10-15 | 29efa2d | 7,984 B | B | view · diff |
| git:20261014.0f16275 | 2026-10-14 | 0f16275 | 7,983 B | B | view · diff |
| git:20261013.86f2ade | 2026-10-13 | 86f2ade | 7,953 B | B | view · diff |
| git:20260930.5675523 | 2026-09-30 | 5675523 | 7,965 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7925 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
vzakharov/muthur · 22 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hmjka2qyjtcyr6iu GET https://markdownregistry.com/api/v1/resolve?ref=vzakharov/muthur/check-merge GET https://markdownregistry.com/api/v1/blob/7f4ab8793922a818ace4a60344de8230f6890622960a742fb1d689cd77ba8dff
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.