Agent Skills › dartsim/dart › dart-release-packaging

dart-release-packaging

GitHub

用于DART项目发布打包，自动执行版本递增、分支创建、文件更新及变更日志生成，并在推送到远程和创建PR前获取用户确认。

.codex/skills/dart-release-packaging/SKILL.md dartsim/dart

Trigger Scenarios

需要为DART项目创建新版本发布执行发布流程中的版本号和变更日志更新

Install

npx skills add dartsim/dart --skill dart-release-packaging -g -y

More Options

Non-standard path

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

Use without installing

npx skills use dartsim/dart@dart-release-packaging

指定 Agent (Claude Code)

npx skills add dartsim/dart --skill dart-release-packaging -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-release-packaging",
    "description": "DART Release Packaging: create a release version bump and changelog PR"
}

dart-release-packaging

Use this skill in Codex to run the DART dart-release-packaging 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-release-packaging <arguments>
Codex: $dart-release-packaging <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

Create release packaging PR after explicit maintainer/user approval: $ARGUMENTS

Required Reading

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

Workflow

Confirm the new version, for example 6.16.6.
Derive the release branch: release-<major>.<minor>.

Fetch and branch from the release branch:

git fetch origin <RELEASE_BRANCH>
git checkout -B release/<NEW_VERSION>-version-bump origin/<RELEASE_BRANCH>

Bump versions in package.xml and pixi.toml.
Update version requirements in examples/tutorials if needed.
Invoke the dart-changelog routine in release-audit mode, then add or finalize the CHANGELOG.md release section with the release date, milestone link, release summary, and audit from docs/onboarding/changelog.md.
Run pixi run lint and relevant packaging checks.
Commit as Packaging <NEW_VERSION>.
Ask for explicit maintainer/user approval before pushing, creating the PR, or setting milestones.
After approval, create the PR against the release branch with the release milestone for that branch, for example the specific version milestone if available.