solo-repo-branch-protection-stable-gate-and-self-merge SKILL.md skillA
solo-repo-branch-protection-stable-gate-and-self-merge from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/solo-repo-branch-protection-stable-gate-and-self-merge@v1.0.1Pins v1.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/solo-repo-branch-protection-stable-gate-and-self-merge/SKILL.md- Versions recorded
- 6
- Latest version
- v1.0.1, committed Sep 17, 2026
- First version recorded
- Aug 10, 2026
- Size
- 7,704 bytes
- Repository stars
- 3
- License
- MIT
Lock main on a solo repo so nothing red lands and you are not locked out — no second reviewer needed. Use when something broken reached main by direct push (CI runs too late to block it), or status checks are required and pushes still land. Traps: a matrix names check runs `test (20)`/`test (22)`, not the workflow name, so require a stable aggregation gate that fails, not skips; `required_status_checks` gates merges, not pushes; and `required_approving_review_count: 0` is what lets you…
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
# Solo-Repo Branch Protection: Stable Gate + Self-Merge ## Problem You want main to be unbreakable — no direct pushes, the test check must be green before anything lands — but you're the only maintainer, so you can't require a second reviewer, and you don't want a config that deadlocks all merges later. Three traps make the naive approach wrong. ## Context / Trigger Conditions - A broken/malformed commit reached `main` because it was pushed directly (CI runs *after* the push lands, so a post-push workflow can't block it). - You set "require status checks to pass" but direct pushes still go through. - You're a solo owner and worry branch protection means you can never merge your own PRs. ## Solution ### Trap 1 — Matrix check-runs aren't named after the workflow A workflow `name: Tests` with a job `test` and `strategy.matrix.node-version: [20, 22]` produces check-runs named **`test (20)`** and **`test (22)`** — not `Tests`. If you require `Tests` (the workflow name) as a status check, it never exists → no merge ever satisfies it. If you require `test (20)`/`test (22)` directly, then changing the matrix …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/solo-repo-branch-protection-stable-gate-and-self-merge@sha256:af98fc15b868538dThe line at the top of this page pins the label v1.0.1, 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_3gy4pekff76pttt4)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 10, 2026 and Sep 17, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-09-17 | 9d1df51 | 7,704 B | A | view · diff |
| v1.0.1 | 2026-09-11 | 2d7d978 | 7,313 B | A | view · diff |
| v1.0.0 | 2026-08-12 | 9a8e5a8 | 7,073 B | A | view · diff |
| v1.0.0 | 2026-08-10 | 5b6d8a2 | 6,994 B | A | view · diff |
| v1.0.0 | 2026-08-10 | 99d749c | 6,975 B | A | view · diff |
| v1.0.0 | 2026-08-10 | a58c34c | 6,343 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 (7704 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
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3gy4pekff76pttt4 GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/solo-repo-branch-protection-stable-gate-and-self-merge GET https://markdownregistry.com/api/v1/blob/af98fc15b868538d476bf4de497d8648f01b2c8e8e0c8a8e3e2ab95db470dc54
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.