agentsclimarketplace
Sign in

Semantic release beta

Skill oleg-koval/agent-skills/packages/software-development/semantic-release-beta/adapters/cursor/skills/semantic-release-beta

Set up or update a Node.js release pipeline that uses semantic-release-npm-github-publish with a stable main channel and a prerelease beta channel on a beta branch, including GitHub Actions validation and npm publishing behavior.From its SKILL.md

Install
npx -y skills add oleg-koval/agent-skills --skill semantic-release-beta

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.4 KB, 404 tokens by cl100k_base, as published. Nobody here has run it

<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->

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

  1. 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 prereleases
  4. 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

What ships with it: 4 files

3.0 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.