odin-release

Plugin odin-release from marketplace odin-marketplace in OutlineDriven/odin-claude-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (13)

• autoship

  Use when the user says release this, publish this package, or cut a release for a changesets-based npm package. Not for non-npm packages or releases without a changesets workflow.

• changelog-updates

  Use when a release or a since-tag window needs user-facing release notes drafted. Not for publishing the release.

• cherrypick-to-release

  Use when the user asks to cherry-pick, backport, or apply a hotfix to a release branch. Not for merging feature branches or cutting new release branches.

• cut-new-release-candidate

  Use when the user asks to cut, trigger, or start a release candidate for a release branch. Not for full releases, hotfixes, or non-release-candidate workflow dispatches.

• merge-and-deploy

  Use when a human runs /merge-and-deploy to merge a PR and trigger or verify deployment. Don''t use for tasks that require source changes or without explicit human confirmation at each gate.

• open-source-license-selection

  Use when the user asks to choose, reconcile, or apply an open-source license and package metadata. Not for readiness auditing.

• open-source-readiness-audit

  Use when the user asks whether a repository is ready for public release or wants a gap assessment. Not for choosing or applying a license: use open-source-license-selection.

• post-release-status

  Use when a user asks to post, update, or check cherry-pick status for a release as a single Slack Block Kit board. Not for mutating pull requests or posting to multiple messages.

• prepare-repository-for-public-release

  Use when asked to prepare a repository for public launch or open source it. Not for remote, credential, publish, deploy, or irreversible changes.

• release-gate

  Use when the user decides to ship a release as a signed tag or a redaction-gated PR. Modes: tag (default) and pr. Not for running workflow-owned steps by hand: use the CI/CD workflow.

• release-landing-report

  Use when the user runs /release-landing-report to summarize landed changes and return a landing summary report. Not for tasks that require source or remote-system changes.

• secure-npm-package

  Use when creating or hardening an npm release with Trusted or Staged Publishing, including E404 packages sequenced after first publish. Not for remote changes or publishing.

• shipping

  Use when deploying to production, planning a feature release, setting up launch safeguards, or running a canary release. Not for local dev deploys or deploys without a confirmed rollback plan.

Similar plugins