skills.rest
rvdbreemen
rvdbreemenCOMMUNITY
Explore all skills by this author →
GitHub

beta-prerelease

Publish OTGW-firmware beta prereleases with GitHub release artifacts.

199|41|Updated Oct 25, 2020
Search Tags:#versioning#github#discord#ci-cd#prerelease#otgw-firmware#firmware build
One-click install
npx skills add https://github.com/rvdbreemen/OTGW-firmware --skill beta-prerelease
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: beta-prerelease
Source: https://github.com/rvdbreemen/OTGW-firmware/tree/main/.claude/skills/beta-prerelease
Command: npx skills add https://github.com/rvdbreemen/OTGW-firmware --skill beta-prerelease

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines publishing OTGW firmware beta prereleases so field testers can validate changes quickly without risking stable release behavior.

Core Features & Use Cases

  • Automated prerelease bumping: Increments _VERSION_PRERELEASE using bin/bump-prerelease.sh and prepares a properly formed prerelease tag.
  • Narrative and release integrity: Refreshes README, CHANGELOG, and beta release notes digest content to keep the published prerelease page accurate.
  • Verified build and evaluation: Runs firmware build verification and a quick evaluator pass before creating and publishing the GitHub prerelease.
  • Tester communication workflow: Announces the prerelease to Discord #beta-testing with a diff link against the latest stable release.

Quick Start

Run the skill and let it bump the prerelease version, build, publish the GitHub prerelease, and post the announcement to Discord for field testing.

Frequently Asked Questions about beta-prerelease

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a GitHub prerelease for firmware field testing?▼

Automating a GitHub prerelease for firmware field testing requires bumping the prerelease version, verifying the build, creating a tag, and publishing release artifacts for testers to validate changes quickly.

What is a prerelease versioning workflow for CI/CD firmware builds?▼

A prerelease versioning workflow for CI/CD firmware builds increments the prerelease version identifier, runs build verification and evaluator passes, and publishes tagged GitHub artifacts before a stable release.

How do I announce a beta prerelease to Discord from a GitHub workflow?▼

Announcing a beta prerelease to Discord from a GitHub workflow involves posting a message to a beta-testing channel that includes a diff link comparing the new prerelease tag against the latest stable release.

Does the OTGW-firmware prerelease process update the changelog and README?▼

Yes, the OTGW-firmware prerelease process updates the changelog, README, and beta release notes digest content to ensure the published GitHub prerelease page remains accurate for field testers.

When should I use a beta prerelease instead of a stable firmware release?▼

You should use a beta prerelease instead of a stable firmware release when changes on the dev branch need many-times-in-one-cycle validation by field testers without risking stable release behavior.

Do I need to run a firmware build verification before publishing a GitHub prerelease?▼

Yes, you need to run firmware build verification and a quick evaluator pass before creating and publishing the GitHub prerelease to ensure release integrity and prevent broken artifacts.

Related Skills

Explore More Software Engineering Skills→
rvdbreemenrvdbreemen
199

update-docs

Update OTGW-firmware documentation from git diffs via a sequential backlog workflow.

Community
Advanced
seasonmacseasonmac

openclaw-release-maintainer

Coordinate OpenClaw release management across npm, GitHub, and Sparkle feeds.

Community
Advanced
a-ariffa-ariff
14

verification-before-completion

Enforce a five-step verification gate before claiming task completion.

Community
Intermediate
SafeAI-Lab-XSafeAI-Lab-X
1.0k

openclaw-release-maintainer

Coordinate OpenClaw release workflows to validate versions, changelogs, and publish readiness.

Community
Advanced