Individual skill
bridge-promote
Promote CORE changes from your user branch to upstream by scope (core to OSS upstream, org to org overlay). Runs mandatory content-safety checks, opens fork-based PRs. For file-level contributions use bridge-contribute. Trigger: "/bridge-promote", "promote", "cherry-pick", "push to upstream".
skills/bridge-promote/SKILL.md
Source commit 2554bda8eeb2d55671e922c31484905fc8c67af9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 13
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-memory Repository topic
- agent-orchestration Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- coding-agent Repository topic
- context-engineering Repository topic
- copilot-cli Repository topic
- developer-tools Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,065 bytesSKILL.mdcore · 7,065 bytesreferences/workflow.mddoc · 17,273 bytes
Read excerpt
# Bridge Promote — Scope Routing
Routes commits from `user/*` to the right upstream based on `scope:`
frontmatter (or path inference). See docs/org-overlays.md (tier model). A root `CLAUDE.md` classifies `user` and never promotes.
| Commit scope | Goes to | How |
|---|---|---|
| `scope: core` (or unset, on CORE-allowlist path) | the upstream with **`scope: core`** (e.g. `bks-lab/open-bridge:main`) plus any org/personal overlay that also carries it | Cherry-pick to local `development`, then PR to the OSS upstream |
| `scope: org` | the upstream with **`scope: org`** only (your org overlay, e.g. `<your-org>/<your-bridge>:development`) | Cherry-pick + PR to that repo, **unless it is a flat mirror** (below): then refuse and export |
| `scope: personal` | the upstream with **`scope: personal`** only (your personal overlay) | Same as `org`: cherry-pick + PR, or refuse and export for a flat mirror |
| `scope: user` / `private` | **stays local** on `user/{name}` | No-op |
**Destination selection is by SCOPE, never by `role:` alone.** For a
commit/file of scope `S`, the destination is the `bridge-config.yaml.upstreams[]`