| 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 lives in .claude/commands/; this file is its generated adapter
in the shared .agents/skills/ catalog.
Invocation
- Claude Code:
/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
@docs/onboarding/changelog.md
Workflow
For a source change that depends on 3D structure or behavior, use the target
branch's dart-verify-sim workflow to preserve the text oracle and assessed
visual evidence, or record why the target branch cannot render the claim.
- 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>
- For AI-infra or workflow-doc backports, compare the release branch capability
inventory and adapter directories against
main. If the release branch has a
smaller workflow surface, adapt to the release branch instead of importing
main-only workflows.
