Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →yeachan-heo/release
Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASE_RULE.md, then guides the release
Passed 15 of 20 test cases with the skill, and 11 of 20 without it.
and 5 more in the full report
6 fixed11 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
When committing bumped version files and CHANGELOG.md during execution, what commit message format should be generated?
| Checked | Without skill | With skill |
|---|---|---|
| Uses the Conventional Commit format `chore(release): bump version to vX.Y.Z`. | Missed | Passed |
The instructions your model reads when the skill loads.
A thin, repo-aware release assistant. On first run it inspects the project and CI to derive release rules, stores them in .omc/RELEASE_RULE.md for future use, then walks you through a release using those rules.
/oh-my-claudecode:release [version]
version is optional. If omitted the skill will ask. Accepts patch, minor, major, or an explicit semver like 2.4.0.--refresh to force re-analysis of the repo even when a cached rule file exists.Check whether .omc/RELEASE_RULE.md exists.
If it does NOT exist (or --refresh was passed): Run the full repo analysis below and write the file.
If it DOES exist: Read the file. Then do a quick delta check — scan .github/workflows/ (or equivalent CI dirs: .circleci/, .travis.yml, Jenkinsfile, bitbucket-pipelines.yml, gitlab-ci.yml) for any modifications newer than the last-analyzed timestamp in the rule file. If relevant workflow files changed, re-run the analysis for those sections and update the file. Report what changed.
Inspect the repo and answer the following. Write answers into .omc/RELEASE_RULE.md.
package.json / pyproject.toml / Cargo.toml / build.gradle / VERSION file / etc.scripts/release.*, Makefile release target, bump2version, release-it, semantic-release, changesets, goreleaser).package.json with publishConfig or npm publish in CI), PyPI (pyproject.toml + twine/flit), Cargo (Cargo.toml), Docker (Dockerfile + push step), GitHub Packages, other.test cases passed, vs 11 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.