Orchestrate oh-my-droid npm releases with version synchronization and publishing.
npx skills add https://github.com/MeroZemory/oh-my-droid --skill release-merozemory
Please help me install this Agent Skill. Skill: release Source: https://github.com/MeroZemory/oh-my-droid/tree/main/skills/release Command: npx skills add https://github.com/MeroZemory/oh-my-droid --skill release-merozemory
It removes the manual chore of synchronizing versions across oh-my-droid's package, installer code, plugin metadata, tests, and documentation while running the full release pipeline.
Use the release skill to execute /release patch or your chosen semantic level and the workflow will update versions, run tests, tag, publish, and create the release for you.
High-intent search queries and answers about installing and using this skill.
Automating npm package releases requires synchronizing version strings across package.json, installer constants, plugin metadata, and README badges before running tests and publishing. This workflow orchestrates semantic version bumps, tagging, and npm publish in one guided checklist to ensure consistency across all release artifacts.
Bumping semantic versions for a plugin involves applying patch, minor, or major release increments while synchronizing version strings across package files, installer constants, and test expectations. This automated release workflow ensures tests, documentation badges, and metadata reflect the new version before deployment.
Running npm tests and creating GitHub tags automatically during deployment is supported by this release orchestration workflow. It executes tests, commits version changes, creates GitHub tags, publishes to npm, and generates release notes sequentially to maintain deployment integrity.
The release workflow supports patch, minor, and major semantic version increments for npm packages. It applies the selected version bump across package.json, installer constants, plugin metadata, and test expectations, ensuring all components align before publishing to npm and tagging on GitHub.
Before publishing an npm package, version synchronization is required across package.json, installer constants, plugin.json metadata, README badges, and test expectations. The workflow updates all these files automatically to prevent version mismatches between the package, installer, and marketplace listings.
npm release tests fail when version strings are mismatched because test expectations, package.json, and plugin metadata must reference identical semantic versions. This workflow resolves the issue by synchronizing all version strings before running tests, tagging, and publishing to prevent inconsistent release states.
sachinnair90Coordinate safe software releases with semver, Git tags, GitHub Releases, and npm publication.
outfitter-devPackage and distribute Claude Code plugins with versioning and GitHub releases.
voidrotGenerate changelogs and release notes from commit history and tags.
bmad-code-orgAutomates npm release process including changelog drafting, versioning, git tagging, publishing, and GitHub releases.
