Agent Skills › dartsim/dart › dart-backport-pr

dart-backport-pr

GitHub

用于将已合并到 main 分支的 PR 或提交 cherry-pick 到指定发布分支，自动处理冲突检查、运行测试并生成新的 Backport PR。

.codex/skills/dart-backport-pr/SKILL.md dartsim/dart

Trigger Scenarios

需要将 main 分支的功能或修复同步到旧版本发布分支用户请求创建 backport pull request

Install

npx skills add dartsim/dart --skill dart-backport-pr -g -y

More Options

Non-standard path

npx skills add https://github.com/dartsim/dart/tree/main/.codex/skills/dart-backport-pr -g -y

Use without installing

npx skills use dartsim/dart@dart-backport-pr

指定 Agent (Claude Code)

npx skills add dartsim/dart --skill dart-backport-pr -a claude-code -g -y

安装 repo 全部 skill

npx skills add dartsim/dart --all -g -y

预览 repo 内 skill

npx skills add dartsim/dart --list

SKILL.md

Frontmatter

{
    "name": "dart-backport-pr",
    "description": "DART Backport PR: backport a merged main PR to a release branch"
}

dart-backport-pr

Use this skill in Codex to run the DART dart-backport-pr workflow. The editable workflow source currently lives in .claude/commands/, and this generated Codex skill is a first-class Codex entrypoint.

Invocation

Claude Code/OpenCode: /dart-backport-pr <arguments>
Codex: $dart-backport-pr <arguments>

Treat the text after the skill name as $ARGUMENTS. When the workflow references $1, $2, etc., map those to the positional values supplied by the user.

Command Body

Backport PR or commits: $ARGUMENTS

Required Reading

@AGENTS.md @docs/onboarding/contributing.md @docs/onboarding/release-management.md

Workflow

Verify the source PR or commit is merged to main:

gh pr view <SOURCE_PR> --json state,mergedAt,baseRefName,mergeCommit

Check whether an equivalent change already exists on the release branch:

git fetch origin <RELEASE_BRANCH> main
git cherry -v --abbrev=40 origin/<RELEASE_BRANCH> origin/main | grep <COMMIT_HASH>

Create a release branch from the release target:

git checkout -B backport/<SOURCE_PR>-to-<RELEASE_BRANCH> origin/<RELEASE_BRANCH>

Cherry-pick with provenance: git cherry-pick -x <COMMIT_HASH>.
Resolve conflicts minimally; stop and ask if conflicts are broad or change behavior.
Run pixi run lint and the smallest relevant release-branch checks.
Ask for explicit maintainer/user approval before pushing or opening the PR. After approval, open the PR against the release branch with milestone matching that release branch and use the PR template.