merge-downstream SKILL.md skillA
merge-downstream from gems-uff/noworkflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gems-uff/noworkflow/merge-downstream@git:20261019.85a4863Pins git:20261019.85a4863 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gems-uff/noworkflow
- Path
.claude/skills/merge-downstream/SKILL.md- Versions recorded
- 8
- Latest version
- git:20261019.85a4863, committed Oct 19, 2026
- First version recorded
- Oct 14, 2026
- Size
- 21,238 bytes
- Repository stars
- 130
- License
- MIT
Brings main into an issue branch and checks that it came in whole — including what git cannot see. Use when bringing a branch that fell behind up to date, when auditing a merge someone else made, or before accepting a branch for integration.
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
# Merging main into the branch
Bringing `main` into an issue branch is routine, and because it is routine it
runs on autopilot. Two things go wrong silently: **content of `main` lost in
the resolution of a conflict**, and **an incompatibility that only exists
after the merge**, which git has no way of seeing. Both are detected by
measurement, not by reading.
The script `check_merge.sh`, in this skill's directory, runs the mechanical
checks in one go, from anywhere inside the repository:
```bash
"$(git rev-parse --show-toplevel)"/.claude/skills/merge-downstream/check_merge.sh [merge-commit] [upstream] [upstream-parent]
```
Without arguments it checks `HEAD` against `origin/main`. The third argument
says which parent is the upstream side, and git's rule decides it: **parent 1
is whatever was checked out when the merge was made.** A merge made on the
branch — `git merge origin/main`, or a `git pull` ("Merge branch 'master' of
<url>") — has the upstream side as parent 2, the default. So does a
`git pull` on a maintainer's own `main`, the merge `main` gets when two
maintainers commit there directly: its upstream side is `origin/main`. A
…Read the whole file at its exact version.
How to install
mdr add gems-uff/noworkflow/merge-downstream@sha256:edaaa2e8200b2b9eThe line at the top of this page pins the label git:20261019.85a4863, 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_ok355w3lrxiuczca)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between Oct 14, 2026 and Oct 19, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.85a4863 latest | 2026-10-19 | 85a4863 | 21,238 B | A | view · diff |
| git:20261019.e6ed8f6 | 2026-10-19 | e6ed8f6 | 21,239 B | A | view · diff |
| git:20261019.d7804ba | 2026-10-19 | d7804ba | 21,256 B | A | view · diff |
| git:20261018.c3db325 | 2026-10-18 | c3db325 | 21,304 B | A | view · diff |
| git:20261018.0313a62 | 2026-10-18 | 0313a62 | 21,250 B | A | view · diff |
| git:20261016.4ea93ec | 2026-10-16 | 4ea93ec | 20,140 B | A | view · diff |
| git:20261015.1ba5b15 | 2026-10-15 | 1ba5b15 | 20,009 B | A | view · diff |
| git:20261014.00066b9 | 2026-10-14 | 00066b9 | 19,953 B | A | view |
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 (21238 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
gems-uff/noworkflow · 130 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ok355w3lrxiuczca GET https://markdownregistry.com/api/v1/resolve?ref=gems-uff/noworkflow/merge-downstream GET https://markdownregistry.com/api/v1/blob/edaaa2e8200b2b9e54173cf76670b4ed253a0f4a49a9e9c99e1f706a6426d14c
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.