Bridge Sync

Bridge Sync — Batch end-of-sprint upstream sync

/bridge-sync is the wide-net complement to /promote and /contribute.

| Skill | Granularity | Use case | |---|---|---| | /promote | per-commit | "promote this batch of recent commits" | | /contribute | per-file | "scan for upstream-worthy files, adapt, PR" | | /bridge-sync | per-sprint | "push EVERYTHING pending to both upstreams now" |

Read the referenced file ONLY when triggered.

When to use

• End of a work-sprint, ready to publish all upstream-worthy changes at once
• After a refactor that touched many CORE+org files — manual cherry-pick is tedious
• When /promote has been deferred for days and there's a backlog
• When you want both bks-lab/open-bridge and your org overlay updated in one operation

NOT for:

• A single commit (/promote is leaner)
• File-level adaptation work (/contribute --adapt does that)
• USER-only changes (those stay local)

Arguments

| Argument | Effect | Default | |---|---|---| | (none) | Full sync to both upstreams | — | | --dry-run | Show routing matrix, don't push | false | | --repo open-bridge | Sync only to open-bridge | both | | --repo | Sync only to your org overlay | both | | --since | Sync commits since this ref (default: last sync tag) | last sync | | --no-scrub | Disable open-bridge scrubbing (DANGER — only for emergency) | false |

Prerequisites

• Current branch must be user/*. Refuses on development / main.
• bridge-config.yaml.upstreams[] defines BOTH upstreams.
• git remote has origin (your fork) + upstream (typically /).
• For open-bridge sync: gh CLI authenticated with cross-fork PR rights.

Decision Tree

User wants to...
├── Full sync (default)                  → references/workflow.md
├── Dry-run / preview routing            → references/workflow.md (stop after Step 4)
├── Sync only one repo                   → references/workflow.md § --repo override
├── Configure scrub patterns             → rules/promote-safety.md per-repo blocklists
└── Tag the sync point                   → references/workflow.md § sync-tag

Safety

/bridge-sync runs a three-layer safety pipeline per destination (see rules/promote-safety.md for the full rule):

1. scrub_rules. — auto-rewrite during cherry-pick. Maps

personal/internal tokens (your username, org, hostnames) to placeholders. Configured in bridge-config.yaml.promote.scrub_rules.

1. content_blocklist. — hard-block scan after scrub. Hits

classify as scrubable (handled by layer 1), adaptable (defer for /contribute --adapt), or personal-PII (refuse).

1. Universal patterns — private keys, API tokens, paths — always

blocked regardless of destination.

A commit hitting an adaptable pattern doesn't block the whole sync — it gets routed as 🟡 in the matrix and deferred. The clean commits still ship. --no-scrub only disables layer 1 (auto-rewrite); layers 2+3 always run.

Workflow recipes for conflict resolution (DU / UU / divergent structure), MIXED-CU cherry-picks, and residual-leak fixup (git commit --fixup + rebase --autosquash) live in references/workflow.md § Step 5.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: bks-lab
• Source: bks-lab/open-bridge
• License: MIT
• Homepage: https://bks-lab.github.io/open-bridge/

Install and usage instructions live in the source repository linked above.