How do I install the Synapseml Branches skill?

Run npx skillmds@latest add microsoft/synapseml-branches in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Synapseml Branches safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Synapseml Branches?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Synapseml Branches free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Synapseml Branches?

Microsoft (@microsoft) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Synapseml Branches by microsoft — Agent Skill

Name: Synapseml Branches
Author: Microsoft

Synapseml Branches

Resolve SynapseML branch-specific rules, runtime baselines, sync policy, and CI expectations. Use before editing, rebasing, merging, testing, or declaring readiness for master, spark3.5, spark4.0, spark4.1, port/sync branches, or a PR whose base branch determines behavior.

Microsoft c896fb6 7 files · 40.1 KB Updated Sep 17, 2026 2.7k repo stars

File contents

SynapseML branch context

Use the PR base branch as the context. A feature branch name does not determine the runtime, sync policy, or CI that must pass.

Workflow

Read root AGENTS.md.
Resolve the target:
- For a PR, read baseRefName from GitHub.
- For direct branch work, use the checked-out shared branch.
Load the mapped reference. Filenames use p for the version decimal:
- master -> branch-spark3p5.md. master is currently the canonical Spark 3.5 development baseline.
- spark3.5 -> branch-spark3p5.md. This is the shared Spark 3.5 release branch.
- spark4.0 -> branch-spark4p0.md.
- spark4.1 -> branch-spark4p1.md.
- Any other target -> branch-fallback.md.
Verify every version, dependency, trigger, skip, and test command against that branch's live build.sbt, environment.yml, workflows, and pipeline.yaml. References are decision guides, not stale-value authority.
Recheck branch context at three points: before implementation, before validation, and immediately before push/readiness. Target movement or a changed base invalidates earlier evidence.

Responsibilities

Ordinary PRs rebase onto their latest target with --force-with-lease.
Shared port branches receive master by merge; never rebase or force-push the shared branch.
For conflict resolution, compare merge base, master, and port branch; ancestry alone does not prove both sides survived.
Inspect CI definitions on the target branch and confirm builds actually queued. Never infer port-branch coverage from master.
Confirm the relevant suites ran by test result/class, not only job status.
Treat .github/skills/ as authoritative. .agents/ is compatibility-only and may contain stale copies.
If no exact reference exists, follow the fallback, state uncertainty, and add a concise reference from the branch template when the branch is an active supported target.

---name: synapseml-branchesdescription: Resolve SynapseML branch-specific rules, runtime baselines, sync policy, and CI expectations. Use before editing, rebasing, merging, testing, or declaring readiness for master, spark3.5, spark4.0, spark4.1, port/sync branches, or a PR whose base branch determines behavior.---# SynapseML branch contextUse the PR base branch as the context. A feature branch name does not determinethe runtime, sync policy, or CI that must pass.## Workflow1. Read root `AGENTS.md`.2. Resolve the target: - For a PR, read `baseRefName` from GitHub. - For direct branch work, use the checked-out shared branch.3. Load the mapped reference. Filenames use `p` for the version decimal: - `master` -> [branch-spark3p5.md](references/branch-spark3p5.md). `master` is currently the canonical Spark 3.5 development baseline. - `spark3.5` -> [branch-spark3p5.md](references/branch-spark3p5.md). This is the shared Spark 3.5 release branch. - `spark4.0` -> [branch-spark4p0.md](references/branch-spark4p0.md). - `spark4.1` -> [branch-spark4p1.md](references/branch-spark4p1.md). - Any other target -> [branch-fallback.md](references/branch-fallback.md).4. Verify every version, dependency, trigger, skip, and test command against that branch's live `build.sbt`, `environment.yml`, workflows, and `pipeline.yaml`. References are decision guides, not stale-value authority.5. Recheck branch context at three points: before implementation, before validation, and immediately before push/readiness. Target movement or a changed base invalidates earlier evidence.## Responsibilities- Ordinary PRs rebase onto their latest target with `--force-with-lease`.- Shared port branches receive `master` by merge; never rebase or force-push the shared branch.- For conflict resolution, compare merge base, `master`, and port branch; ancestry alone does not prove both sides survived.- Inspect CI definitions on the target branch and confirm builds actually queued. Never infer port-branch coverage from `master`.- Confirm the relevant suites ran by test result/class, not only job status.- Treat `.github/skills/` as authoritative. `.agents/` is compatibility-only and may contain stale copies.- If no exact reference exists, follow the fallback, state uncertainty, and add a concise reference from the [branch template](references/branch-template.md) when the branch is an active supported target.

Frequently asked questions