Automate the release process by updating the changelog, manifest files, and
Automates release process by updating changelog, manifest files, and creating git tags. Use this when you're ready to cut a new release version.
/plugin marketplace add cbrake/claude-plugins/plugin install doc-driven-development@cbrakeAutomate the release process by updating the changelog, manifest files, and creating a git tag.
Steps:
Read @CLAUDE.md to find the list of manifest files under the "Release Management" section. These files contain version numbers that need to be updated.
Read the CHANGELOG.md file to find:
## [X.Y.Z] format)## [Unreleased] section that needs to be convertedDetermine the release version:
/release 2.0.0)## [Unreleased] section exists, calculate the next version by
incrementing the patch version (e.g., 1.0.6 → 1.0.7)## [Unreleased] section exists, use the latest version found in the
changelogUpdate CHANGELOG.md:
## [Unreleased] with
## [X.Y.Z] - <current date in YYYY-MM-DD format>## [Unreleased] section at the top for new changes.Update version in all manifest files listed in CLAUDE.md:
"version":, version =, version:, etc.)Create a git tag for the version:
v<version> (e.g., v1.0.7)git tag v<version> to create the tagProvide a summary showing:
git push --tagsImportant: Do not push tags or commit changes automatically. Let the user review and push when ready.
/releasePrepare a new release by updating changelog, version, and documentation