backport Skill
Backport changes (current branch, a PR, a branch, or specific commits/SHAs) onto a target branch (typically a release branch like rel/). Use when the user says "backport this", "backport PR ...", "cherry-pick to <branch", or asks to port commits to another branch. Handles stashing uncommitted work, branch creation, che Published by microsoft in vscode-cosmosdb.
What is backport Skill?
Backport changes (current branch, a PR, a branch, or specific commits/SHAs) onto a target branch (typically a release branch like rel/). Use when the user says "backport this", "backport PR ...", "cherry-pick to <branch", or asks to port commits to another branch. Handles stashing uncommitted work, branch creation, che Published by microsoft in vscode-cosmosdb. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using vscode-cosmosdb
Technical details
- Install or run with Copy skill directory
When to use backport Skill
- Use it for developers using vscode-cosmosdb.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-cosmosdb
- Skill file: .github/skills/backport/SKILL.md
What it does
Backport changes (current branch, a PR, a branch, or specific commits/SHAs) onto a target branch (typically a release branch like rel/). Use when the user says "backport this", "backport PR ...", "cherry-pick to <branch", or asks to port commits to another branch. Handles stashing uncommitted work, branch creation, che
Skill instructions
Backport Skill Create a backport pull request that applies changes from a source (current branch, a PR, another branch, or specific commits) onto a target branch — interactively, from the local workspace. The target is typically a release branch (e.g. rel/0.32), but any existing branch is allowed except the source's own base branch (a backport onto the same base is a no-op). Inputs to resolve Before running any git commands, determine: 1. Source — one of: - Current branch (default if the user says "backport this" without specifying). - PR number (e.g. "backport PR 1234"). - Branch name. - Commit SHA(s) or range. 2. Target branch — any existing branch on origin. Typical case is a release branch (rel/). If the user did not specify, list candidates with git branch -r --list 'origin/rel/' first; if none match or the user wants something else, fall back to git branch -r and ask. Refuse the source's own base branch (e.g. if the PR or current branch already targets main, refuse main; if it ta
Explore related resources
Frequently asked questions
What is backport?
backport is a open-source AI agent skill with Copy skill directory. Backport changes (current branch, a PR, a branch, or specific commits/SHAs) onto a target branch (typically a release branch like rel/).
Who is backport best for?
backport is best for reusing agent instructions, scripts, and references.
How do I install backport?
Install or run backport using Copy skill directory. Check backport for the latest setup command.
Is backport actively maintained?
backport may need a closer maintenance check before production use.
Auto-fetched from GitHub.
