workflow-branch-sync SKILL.md skillB
workflow-branch-sync from lugassawan/swe-workbench is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lugassawan/swe-workbench/workflow-branch-sync@git:20261004.6c46130Pins git:20261004.6c46130 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lugassawan/swe-workbench
- Path
skills/workflow-branch-sync/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261004.6c46130, committed Oct 4, 2026
- First version recorded
- Aug 11, 2026
- Size
- 29,009 bytes
- Repository stars
- 3
- License
- MIT
Sync the current branch with the default branch via rimba or git, then resolve conflicts file by file with a per-hunk rationale and a keep-mine / keep-main / manual recommendation before staging. Push only happens after explicit confirmation — never automatic.
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
# Workflow: Branch Sync
**Announce at start:** "I'm using the workflow-branch-sync skill to bring this branch up to date and help resolve any conflicts."
## When to Invoke
- User's branch has fallen behind the default branch and they want it brought up to date.
- User asks for help resolving merge/rebase conflicts, or wants guidance on "which side is correct".
- Invoked by `/swe-workbench:sync`.
## What This Skill Does NOT Do
- Does not open, merge, or comment on a PR — that is `swe-workbench:workflow-commit-and-pr` / the user's action. Sole exception: Step 7.5 may trim provably-stale scope tags from the open PR's title (reported in the summary) — never pushes, comments, or merges.
- Does not resolve any conflict without first showing both sides and a recommendation with rationale.
- Does not auto-push — ever. The push is a separate, explicitly prompted step at the end.
- Does not rewrite history beyond the single merge or rebase the user asked for.
## Sync Contract
### Step 1 — Preflight Guard
```bash
command -v swe-workbench-skill-script >/dev/null 2>&1 || {
echo "swe-workbench runtime commands not on PATH — reinstall or update the swe-workbench plugin." >&2
exit 1
}
…Read the whole file at its exact version.
How to install
mdr add lugassawan/swe-workbench/workflow-branch-sync@sha256:458b708754dc239bThe line at the top of this page pins the label git:20261004.6c46130, 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_jl4g2gvr3in4xa4b)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 11, 2026 and Oct 4, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261004.6c46130 latest | 2026-10-04 | 6c46130 | 29,009 B | B | view · diff |
| git:20261004.f5a31ff | 2026-10-04 | f5a31ff | 26,955 B | B | view · diff |
| git:20260927.ec10c6e | 2026-09-27 | ec10c6e | 25,451 B | B | view · diff |
| git:20260824.7da1247 | 2026-08-24 | 7da1247 | 23,082 B | B | view · diff |
| git:20260811.925e30f | 2026-08-11 | 925e30f | 22,606 B | B | view |
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (29009 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
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
lugassawan/swe-workbench · 3 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jl4g2gvr3in4xa4b GET https://markdownregistry.com/api/v1/resolve?ref=lugassawan/swe-workbench/workflow-branch-sync GET https://markdownregistry.com/api/v1/blob/458b708754dc239b954a2da0683ad644cb79c4132df6f7ec70a394ba5c6ec5b9
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.