菜单
Guidelines for maintaining external Dart packages, covering versioning, publishing workflows, and pull request management. Use when updating Dart packages, preparing for a release, or managing collaborative changes in a repository.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | dart-package-maintenance |
| description | Guidelines for maintaining external Dart packages, covering versioning, publishing workflows, and pull request management. Use when updating Dart packages, preparing for a release, or managing collaborative changes in a repository. |
| key_features | ["Versioning & CHANGELOG sync","Publishing workflow guidelines","Pull request management"] |
Guidelines for maintaining Dart packages in alignment with Dart team best practices.
To find maintenance tasks or inconsistencies:
Ensure the latest version in CHANGELOG.md matches pubspec.yaml:
CHANGELOG.md with the version: field in
pubspec.yaml.0.major.minor+patch.1.0.0 as soon as the package is stable.Check Published Versions: Before modifying CHANGELOG.md or
pubspec.yaml, ALWAYS check the currently released version (e.g., via
git tag or pub.dev).
Do Not Amend Released Versions: Never add new entries to a version header that corresponds to a released tag.
Increment for New Changes: If the current version in pubspec.yaml
matches a released tag, increment the version (e.g., usually to -wip) and
create a new section in CHANGELOG.md.
Consistency: The CHANGELOG.md header must match the new
pubspec.yaml version.
SemVer Guidelines:
2.0.0-wip, 0.5.0-wip).1.1.0-wip, 0.4.5-wip).1.0.1-wip).CHANGELOG.md should focus on changes
visible to or impacting the end-user (e.g., new features, bug fixes,
breaking changes).pubspec.yaml and CHANGELOG.md with a -wip suffix (e.g., 1.1.0-wip).-wip suffix from pubspec.yaml and
CHANGELOG.md in a dedicated pull request.dart pub publish (or flutter pub publish) and resolve
all warnings and errors.v1.2.3package_name-v1.2.3git tag v1.2.3 && git push --tagsmain into the PR branch rather than
rebasing to resolve conflicts. This preserves the review history and comments.gh pr checkout <number> to inspect changes
locally in your IDE.Profile Dart command-line applications using the VM Service protocol to capture CPU samples and identify performance bottlenecks. Helps agents automate CPU profiling, generate function call breakdown summaries, and export JSON profiles without a browser or DevTools.
General best practices for Dart development. Covers code style, effective Dart, and language features.
Best practices for validating Dart documentation comments. Covers using `dart doc` to catch unresolved references and macros.
Guidelines for handling long lines in Dart code to adhere to the 80-column rule. The `lines_longer_than_80_chars` lint.
Best practices for using `expect` and `package:matcher`. Focuses on readable assertions, proper matcher selection, and avoiding common pitfalls.
Guidelines for using modern Dart features (v3.0 - v3.10) such as Records, Pattern Matching, Switch Expressions, Extension Types, Class Modifiers, Wildcards, Null-Aware Elements, and Dot Shorthands.