Agent Skills
› dartsim/dart
› dart-release-merge-main
dart-release-merge-main
GitHub自动化DART项目发布分支合并至main的流程。自动检测版本，执行合并并依据规范解决冲突，运行代码检查，经审批后创建PR并监控CI状态，确保发布质量。
Trigger Scenarios
需要将活跃发布分支合并回主分支
执行DART项目的发布合并工作流
Install
npx skills add dartsim/dart --skill dart-release-merge-main -g -y
SKILL.md
Frontmatter
{
"name": "dart-release-merge-main",
"description": "DART Release Merge Main: merge the active release branch back into main"
}
dart-release-merge-main
Use this skill in Codex to run the DART dart-release-merge-main workflow. The editable
workflow source lives in .claude/commands/; this file is its generated adapter
in the shared .agents/skills/ catalog.
Invocation
- Claude Code/OpenCode:
/dart-release-merge-main <arguments> - Codex:
$dart-release-merge-main <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
Merge release branch into main: $ARGUMENTS
Required Reading
@AGENTS.md @docs/onboarding/release-management.md @docs/onboarding/ci-cd.md
Workflow
- Auto-detect or confirm the active release branch and release version:
git fetch origin git branch -r | grep -oE 'origin/release-[0-9]+\.[0-9]+' | sort -V | tail -1 - Verify the clone is not shallow and a merge base exists.
- Create
merge/<release-branch>-into-mainfromorigin/main. - Merge the release branch with a title like
Merge release-6.19 into main (v6.19.x). - Resolve conflicts using
docs/onboarding/release-management.md:- deleted in main, updated in release: keep deleted
- added in both: prefer main unless release has unique needed content
- content conflicts: prefer main modernization except for manually reviewed changelog entries
- files only on release: keep if still relevant to main
- Verify no unresolved conflicts remain.
- Run
pixi run lintand relevant checks. - Ask for explicit maintainer/user approval before pushing or creating the PR.
After approval, create a PR targeting
mainwith milestoneDART 7.0and use the PR template. - Monitor CI until green.
Output
- PR URL and CI status
- Release branch and release version
- Conflict counts and resolution summary
- Any manual changelog decisions
Version History
- b9fbefc Current 2026-07-19 11:30
