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.

Install it, pinned
mdr add wxxb789/hoa/git-auto-sync-pipelines@git:20261118.d4726de

Pins 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

No tool to install first
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.

The exact contents, by fingerprint
mdr add wxxb789/hoa/git-auto-sync-pipelines@sha256:05fe491adf21811e

The 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_v2h5pxvgcn7qtmzs.svg)](https://markdownregistry.com/a/art_v2h5pxvgcn7qtmzs)

0 badge image fetches in 30 days. What the badge shows.

Ask from your agent
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)

versioncommittedcommitsizeaudit
git:20261118.d4726de latest2026-11-18 d4726de 7,086 BF view · diff
git:20261118.7b3f7602026-11-18 7b3f760 7,129 BF view · diff
git:20261117.5d6cc462026-11-17 5d6cc46 7,157 BF view · diff
v0.1.662026-11-17 fd3bd52 7,161 BF view · diff
v0.1.652026-11-16 e399a8d 7,161 BF view
Keep it current by itself, install once

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.

Install on GitHub

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.

Keep it current by itself

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.

Check a whole project

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

F  16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • 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

GitHub

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.

More from wxxb789/hoa

AGENTS.md AGENTS.md file
wxxb789/hoa · AGENTS.md
git:20261119.6fef477 · audit A · 3 stars
agent-harness-settings-parity SKILL.md skill
wxxb789/hoa · skills/agent-harness-settings-parity/SKILL.md · Audit and apply one policy — model, thinking effort, compaction threshold, approval mode — across every installed…
git:20261117.5d6cc46 · audit A · 3 stars
agent-operating-contract-evolution SKILL.md skill
wxxb789/hoa · skills/agent-operating-contract-evolution/SKILL.md · Evolve an agent's operating contract: its identity file, operating protocol, layered memory / skills / config, and any…
git:20261119.c8fb133 · audit A · 3 stars
ai-coding-agent-delegation SKILL.md skill
wxxb789/hoa · skills/ai-coding-agent-delegation/SKILL.md · Hand a bounded coding or review task to an external autonomous coding-agent CLI in its own git worktree, then verify…
git:20261118.d4726de · audit A · 3 stars
contract-bound-deliverables SKILL.md skill
wxxb789/hoa · skills/contract-bound-deliverables/SKILL.md · Produce a deliverable against an explicit, measurable contract — a length budget, citation discipline, required section…
git:20261119.c8fb133 · audit A · 3 stars
cross-agent-repair-routing SKILL.md skill
wxxb789/hoa · skills/cross-agent-repair-routing/SKILL.md · Get a defect repaired when it sits in another agent's write surface: establish the authority map, rule on the claim…
git:20261117.5d6cc46 · audit A · 3 stars
define-goal SKILL.md skill
wxxb789/hoa · skills/define-goal/SKILL.md · Define ambitious intentions as numbered goal-prompt files, progressing from clear near-term outcomes to provisional…
git:20261117.5d6cc46 · audit A · 3 stars
delegated-work-acceptance SKILL.md skill
wxxb789/hoa · skills/delegated-work-acceptance/SKILL.md · Verify work a teammate or sub-agent reports as done — the artifact, the numbers, and the write boundary — before you…
git:20261118.d4726de · audit A · 3 stars
discord-rich-message SKILL.md skill
wxxb789/hoa · skills/discord-rich-message/SKILL.md · Send structured tables and reports into Discord within its real limits: Components V2 payloads, monospace aligned…
git:20261118.7b3f760 · audit A · 3 stars
dotnet-repo-workflow SKILL.md skill
wxxb789/hoa · skills/dotnet-repo-workflow/SKILL.md · Build, gate and ship a change in a .NET (C#/F#) repo: shell prerequisites, the repo's own gate harness instead of a…
git:20261117.5d6cc46 · audit A · 3 stars
evidence-backed-analytical-writing SKILL.md skill
wxxb789/hoa · skills/evidence-backed-analytical-writing/SKILL.md · Write an evidence-backed analytical report — Chinese policy briefs, capability assessments, or technical arguments that…
git:20261118.7b3f760 · audit A · 3 stars
evidence-boundary-discipline SKILL.md skill
wxxb789/hoa · skills/evidence-boundary-discipline/SKILL.md · State only what a dated source actually supports: fix the tense to the dateline, carry one provenance label across…
git:20261118.d4726de · audit A · 3 stars

Every file in wxxb789/hoa

Browse by kind, by grade F, or by owner.