feat(skills): Add backport-pr skill - #22434
Merged
Merged
Conversation
Adds a skill that backports a merged PR to a maintenance major branch (v10 by default, with a target-major parameter for older majors like v9). It cherry-picks the PR's squash-merge commit, namespaces the commit/PR title scope (e.g. fix(core) -> fix(v10/core)), and opens a draft backport PR following the convention used for the v9 backports. Co-Authored-By: Opus 4.8 <noreply@anthropic.com>
Run verification before finalizing the commit so yarn format changes are folded into the pushed commit instead of left uncommitted. Replace the personal ab/ branch prefix with a neutral backport/ default.
The branch name isn't load-bearing; only the base branch and commit/PR title conventions matter.
The amend replaces the body with the one-line Backport of: note, so drop the contradictory keep-the-body wording. Use a prebuilt namespaced title placeholder so a scope-less source PR yields fix(v10): not fix(v10/):.
gh pr view takes either, so pass the input through unchanged and use the resolved number for the Backport of: reference so URLs render correctly.
Use lint:fix so auto-fixable issues are applied, git add -u so a repo-wide format doesn't stage unrelated edits, and capture the gh pr create URL for the cross-link comment.
The commands now match the prose: amend with the namespaced title for a single squash commit, or fold fixes with --no-edit for multi-commit backports where the title lives on the PR.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 4f530d3. Configure here.
andreiborza
marked this pull request as ready for review
July 22, 2026 09:06
chargome
approved these changes
Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What
Adds a
backport-prskill that backports a merged PR to a maintenance major branch.v10, with a target-major parameter for older majors (e.g.v9).fix(core):becomesfix(v10/core):.Backport of: #<pr>body and cross-links the original.Why
developis now v11 and released changes go onto the previous major's maintenance branch. This codifies the manual convention we used for the v9 backports so it's repeatable and consistent.