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.
npx skills add https://github.com/kevmoo/dash_skills --skill dart-package-maintenance