Individual skill
omh-release-cut
[omh] Shipping a versioned release -- tag it, stage it behind a canary, or roll back the last deploy: decide what goes in, the version, the rollout stages, and a rollback with its trigger and exact command before it is needed. Use when the user says: release-cut, release cut, cut a release, cut the release, cut a new release, tag a release, tag the release, release candidate.
skills/omh-release-cut/SKILL.md
Source commit 98284f305f6a9dce6e36a1580c9f333105f1a950
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 5,442
- Repository last updated
- Nov 11, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- ai-agent Repository topic
- ai-tools Repository topic
- claude-code Repository topic
- codex Repository topic
- hermes-agent Repository topic
- hermes-skill Repository topic
- skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,541 bytesSKILL.mdcore · 9,541 bytesreferences/release-and-rollback-method.mddoc · 3,137 bytes
Read excerpt
# Release Cut
This is a Hermes-native `release-cut` workflow skill.
## Why This Exists
`release-cut` exists because nothing owned deciding a release: `deploy-and-monitor` watches a rollout that is already happening, and a cut, a canary, or a rollback decision reached an image card or a watch lane with no rollback trigger at all.
## First Steps
- State what goes in, what is held back, and the version before proposing the cut.
- Name the rollback trigger and its exact command before the first stage ships.
## Do Not Use When