How do I install the Semantic Release Beta skill?

Run npx skillmds@latest add oleg-koval/semantic-release-beta in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Semantic Release Beta safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Semantic Release Beta?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Semantic Release Beta free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Semantic Release Beta?

oleg-koval (@oleg-koval) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Semantic Release Beta by oleg-koval

Name: Semantic Release Beta
Author: oleg-koval

Semantic Release Beta

Set up or repair a Node.js release pipeline built on semantic-release-npm-github-publish, with a stable channel on main and a prerelease channel on a beta branch, including the GitHub Actions validation and npm publishing behaviour. Use when the user wants "semantic release set up", "a beta release channel", "prerelease publishing", "automated npm publishing", or when an npm package's releases are still manual and should become commit-driven. For writing the notes of a single release use changelog-generator.

oleg-koval 940085a 5 files · 5.2 KB Updated Sep 17, 2026

File contents

semantic-release-beta

Use this skill when a project needs a reusable beta prerelease workflow with:

semantic-release
semantic-release-npm-github-publish
GitHub Actions
a stable main branch
a prerelease beta branch
npm publishing with beta prerelease versions
changelog generation, GitHub releases, npm publishing, and release commits through the maintained preset

Trigger phrases

add a beta release workflow
publish prereleases from a beta branch
set up semantic-release with main and beta
use semantic-release-npm-github-publish
add release validation or dry-run checks in CI

Workflow

Inspect the repository first.
Install or update semantic-release, semantic-release-npm-github-publish, and the peer plugins expected by the preset.
Configure the repo-local semantic-release file to extend semantic-release-npm-github-publish and set branches explicitly:
- main for stable releases
- { name: "beta", channel: "beta", prerelease: "beta" } for prereleases
Add scripts if missing:
- semantic-release: semantic-release
- release:dry-run: semantic-release --dry-run --no-ci
Update GitHub Actions to test both main and beta, validate npm auth, and run release dry-run before real releases.
Preserve existing package manager and Node version policy unless the repo needs the preset's supported Node range.
Use repo-local plugin composition instead of this preset only when the project needs different plugins, different release rules, or full control over plugin upgrade timing.

References

references/preset.md
references/node-semantic-release.md
references/github-actions.md
references/validation.md

---name: semantic-release-betadescription: Set up or repair a Node.js release pipeline built on semantic-release-npm-github-publish, with a stable channel on main and a prerelease channel on a beta branch, including the GitHub Actions validation and npm publishing behaviour. Use when the user wants "semantic release set up", "a beta release channel", "prerelease publishing", "automated npm publishing", or when an npm package's releases are still manual and should become commit-driven. For writing the notes of a single release use changelog-generator.license: MIT---# semantic-release-betaUse this skill when a project needs a reusable beta prerelease workflow with:- `semantic-release`- `semantic-release-npm-github-publish`- GitHub Actions- a stable `main` branch- a prerelease `beta` branch- npm publishing with `beta` prerelease versions- changelog generation, GitHub releases, npm publishing, and release commits through the maintained preset## Trigger phrases- add a beta release workflow- publish prereleases from a `beta` branch- set up `semantic-release` with `main` and `beta`- use `semantic-release-npm-github-publish`- add release validation or dry-run checks in CI## Workflow1. Inspect the repository first.2. Install or update `semantic-release`, `semantic-release-npm-github-publish`, and the peer plugins expected by the preset.3. Configure the repo-local semantic-release file to extend `semantic-release-npm-github-publish` and set branches explicitly: - `main` for stable releases - `{ name: "beta", channel: "beta", prerelease: "beta" }` for prereleases4. Add scripts if missing: - `semantic-release`: `semantic-release` - `release:dry-run`: `semantic-release --dry-run --no-ci`5. Update GitHub Actions to test both `main` and `beta`, validate npm auth, and run release dry-run before real releases.6. Preserve existing package manager and Node version policy unless the repo needs the preset's supported Node range.7. Use repo-local plugin composition instead of this preset only when the project needs different plugins, different release rules, or full control over plugin upgrade timing.## References- `references/preset.md`- `references/node-semantic-release.md`- `references/github-actions.md`- `references/validation.md`

Frequently asked questions