
Dart Package Maintenance
This walks you through the mechanical parts of maintaining a Dart package: checking that your changelog matches pubspec.yaml, following semantic versioning rules, and handling the publish workflow with git tags. It's opinionated about WIP suffixes and warns you not to add changelog entries to already-released versions, which is the kind of mistake you make exactly once before wanting a checklist. The PR guidance is standard (squash commits, merge instead of rebase), but the real value is having versioning rules and pre-publish checks spelled out when you're juggling multiple packages and can't remember if breaking changes mean 0.5.0 or 0.6.0 for unstable versions.
- skills.sh installs
- 285
- GitHub stars
- 148
- last updated
- Aug 21, 2026
Install
$ npx -y skills add kevmoo/dash_skills --skill dart-package-maintenance --agent claude-codeInstalls into .claude/skills of the current project.
Files
Dart Package Maintenance
Guidelines for maintaining Dart packages in alignment with the canonical Dart team External Package Maintenance specification.
When to use this skill
Use this skill when:
- Updating Dart packages, preparing for a release, or managing collaborative changes in a repository.
- Managing versioning,
CHANGELOG.mdsynchronization, and publishing workflows. - Ensuring published packages comply with Dart team conventions.
When NOT to use (Abstention Guardrails)
Do NOT apply package maintenance version bumps or changelog updates when:
Sponsors
Details
- Repository
- github.com/kevmoo/dash_skills
- Category
- Release Management
- First seen
- Jun 3, 2026