release

To automate an npm package release, this skill inspects your repo's version sources and CI publish workflows, caches the rules in `.omc/RELEASE_RULE.md`, and guides you step-by-step through version bumping, testing, git tagging, and publishing based on semver validation.

For monorepo release management, this skill derives repo-specific rules by inspecting CI publishing jobs and release triggers, supporting single-package or monorepo setups across common ecosystems like npm, PyPI, Cargo, and Docker.

Repo-aware rule discovery works by locally inspecting your project's version sources, distribution registry setup, and CI publishing jobs, then caching the derived release rules in a persisted `.omc/RELEASE_RULE.md` file for consistent reuse.

Yes, you can refresh cached release rules by using the `--refresh` flag, which re-analyzes the affected parts of your release configuration and reports the delta changes against your current CI files.

Yes, it supports both tag-driven and workflow-driven release processes by analyzing your repo's specific release triggers and CI publish workflows, then guiding the versioning, testing, tagging, and pushing steps accordingly.

To generate release notes and verify pre-release status, this skill provides an end-to-end walkthrough that helps you pick a semver version, validate a pre-release checklist, draft release notes, and safely execute the bump, test, tag, and publish steps.