sync SKILL.md skillA
sync from axlaser/pitwall is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add axlaser/pitwall/sync@git:20261017.6dc26e3Pins git:20261017.6dc26e3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- axlaser/pitwall
- Path
.claude/skills/sync/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261017.6dc26e3, committed Oct 17, 2026
- First version recorded
- Sep 28, 2026
- Size
- 8,125 bytes
- Repository stars
- 6
- License
- MIT
Fetch the latest upstream branch and merge it into the current branch, in the pitwall repo — feature branches (`dev-<feature>`) sync from `dev`, and `dev` itself syncs from `master`. Stages the merge, walks through any conflicts interactively, then creates the merge commit directly (signed when the user signs commits). Use whenever the user says "sync", "pull dev", "pull master", "update branch", "merge dev", "merge master", "get latest", or anything about bringing upstream changes into their…
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
# /sync — Merge Upstream into Current Branch Fetch the latest upstream branch from origin and merge it into the current branch, walking through any conflicts one file at a time. The merge is staged first (`--no-commit`) so its result can be verified before it's recorded; Claude then creates the merge commit directly, signed only when the user's git config signs commits (the `commit` skill's Step 4.5 decides how). ## Branch model This repo uses a two-tier flow: feature branches (named `dev-<feature>`, e.g. `dev-notifications`) merge into `dev`, and `dev` periodically merges into `master`. This skill picks the sync source automatically from the current branch: - On a feature branch (`dev-<feature>`, or any other branch that isn't `dev`/`master`) → source is `dev`. - On `dev` → source is `master` (pulling in anything that landed on `master` directly, e.g. a hotfix). - On `master` → nothing to sync into — stop. Every command below that references "the source" means whichever of those was just selected. Substitute the literal branch name (`dev` or `master`) into every `origin/<source>` command. ## Step 1 — Pre-flight checks ```bash …
Read the whole file at its exact version.
How to install
mdr add axlaser/pitwall/sync@sha256:e5e87fa0c694ad7eThe line at the top of this page pins the label git:20261017.6dc26e3, 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_2j2bygoiwylig3xb)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 28, 2026 and Oct 17, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.6dc26e3 latest | 2026-10-17 | 6dc26e3 | 8,125 B | A | view · diff |
| git:20261016.6f10095 | 2026-10-16 | 6f10095 | 8,123 B | A | view · diff |
| git:20261015.15ef6c0 | 2026-10-15 | 15ef6c0 | 8,127 B | A | view · diff |
| git:20261014.ef7d605 | 2026-10-14 | ef7d605 | 7,339 B | A | view · diff |
| git:20260928.73a1b71 | 2026-09-28 | 73a1b71 | 7,347 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 (8125 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
axlaser/pitwall · 6 stars · license MIT · pushed 2026-10-17 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_2j2bygoiwylig3xb GET https://markdownregistry.com/api/v1/resolve?ref=axlaser/pitwall/sync GET https://markdownregistry.com/api/v1/blob/e5e87fa0c694ad7e3f6a2bbd2cd3b0e9874544dc3526a804c9d2dbc16d9c3f33
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.