git-auto-sync-pipelines SKILL.md skillF
git-auto-sync-pipelines from wxxb789/hoa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wxxb789/hoa/git-auto-sync-pipelines@git:20261118.d4726dePins git:20261118.d4726de in mdr.lock. Pin the fingerprint instead.
- Audit grade
- F, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wxxb789/hoa
- Path
skills/git-auto-sync-pipelines/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261118.d4726de, committed Nov 18, 2026
- First version recorded
- Nov 16, 2026
- Size
- 7,086 bytes
- Repository stars
- 3
- License
- MIT
Design a scheduled commit/push pipeline for a repo the owner edits by hand: ordered preflight gates, a scope allowlist and size cap, a staged secret scan, rebase-then-push, heartbeat and deduped alerts. Use when a notes or research repo must sync on a schedule, or when an existing auto-sync needs a safety review. Not for a repo with a review/PR workflow, and not for a one-off commit you can make yourself.
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
# Git auto-sync pipelines ## When to Use - A repo is edited by hand (notes vault, research repo) and must be committed and pushed on a schedule. - An existing auto-sync needs a safety review: branch guard, secret scan, alert noise, silent stalls. - Someone asks to "sync these two repos every N hours" without a PR workflow. Scheduled "validate → commit → rebase → push the target branch" for a repo the owner edits by hand. Reference implementation shape: one shared library (`<sync-root>/lib/git-sync-common.sh`) plus one wrapper per repo, run by a single scheduler entry that loops the wrappers and prints only what they printed. A separate watchdog is usually retired into the daily health sweep: "has not succeeded recently" is one step of that sweep, because a periodic watchdog cannot outlive the scheduler it is watching. ## Gate order (never reorder) 1. `flock` — one run at a time; silent skip on contention. 2. pre-staged index → **refuse**. Staging is the human's signal, not the automation's. 3. no-op check → exit silently (still stamp the success heartbeat). 4. branch must equal the target branch. `git push origin HEAD:<target>` from a feature branch …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_v2h5pxvgcn7qtmzs/05fe491adf21811ee1a621bf3ea6816fcc96957bea0d0fe9d73456b8b89d1c42.json
Then /plugin install git-auto-sync-pipelines@markdownregistry-v2h5pxvgcn7qtmzs in Claude Code. It installs git:20261118.d4726de, the one graded F here, pinned to the commit it was graded at, and leaves it there.
mdr add wxxb789/hoa/git-auto-sync-pipelines@sha256:05fe491adf21811eThe line at the top of this page pins the label git:20261118.d4726de, 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_v2h5pxvgcn7qtmzs)
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 wxxb789/hoa/git-auto-sync-pipelines 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 git-auto-sync-pipelines from somewhere else? Ask it: where did my git-auto-sync-pipelines 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 16, 2026 and Nov 18, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261118.d4726de latest | 2026-11-18 | d4726de | 7,086 B | F | view · diff |
| git:20261118.7b3f760 | 2026-11-18 | 7b3f760 | 7,129 B | F | view · diff |
| git:20261117.5d6cc46 | 2026-11-17 | 5d6cc46 | 7,157 B | F | view · diff |
| v0.1.66 | 2026-11-17 | fd3bd52 | 7,161 B | F | view · diff |
| v0.1.65 | 2026-11-16 | e399a8d | 7,161 B | F | 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/git-auto-sync-pipelines/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
- FAIL, critical: No credential-shaped string (matched: AKIAIOSFODNN7EXAMPLE)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7086 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 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
wxxb789/hoa · 3 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_v2h5pxvgcn7qtmzs GET https://markdownregistry.com/api/v1/resolve?ref=wxxb789/hoa/git-auto-sync-pipelines GET https://markdownregistry.com/api/v1/blob/05fe491adf21811ee1a621bf3ea6816fcc96957bea0d0fe9d73456b8b89d1c42
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.