New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release Beta

by Thank-you-Linus in Thank-you-Linus/Linus-Dashboard

Create a beta pre-release for community testing with intelligent version detection.

MITAuto-check passedDevelopment

Install Release Beta

skills CLI
$ npx skills add Thank-you-Linus/Linus-Dashboard --skill release-beta -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Thank-you-Linus/Linus-Dashboard release-beta --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Thank-you-Linus/Linus-Dashboard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-beta .claude/skills/release-beta && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
release-beta
GitHub stars
211
Token cost
~2k tokens
SKILL.md length
879 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Create a beta pre-release for community testing with intelligent version detection.

  • Works in 6 steps: Version Detection & Analysis → Version Type Decision (First Beta Only) → Release Notes Generation & Editing → …
  • Creating beta releases
  • SKILL.md covers ⚠️ CRITICAL TAG FORMAT RULE, Intelligent Workflow, Phase 1: Version Detection &… and Phase 2: Version Type Decision…, plus 11 more sections
  • Calls git, bash and npm

What it does

Release Beta is an agent skill from Thank-you-Linus/Linus-Dashboard. Create a beta pre-release for community testing with intelligent version detection. Use when creating beta releases, publishing pre-releases, or preparing versions for community testing.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: Elevate your smart home experience with a modern, responsive dashboard built on Home Assistant. Effortlessly manage your devices, areas and floors with an intuitive interface…. The licence is MIT.

When your agent uses it

  • Creating beta releases
  • Publishing pre-releases
  • Preparing versions for community testing

Example prompts

  • “/release-beta”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Version Detection & Analysis
  2. Version Type Decision (First Beta Only)
  3. Release Notes Generation & Editing
  4. Quality Validation (BLOCKING)
  5. Final Approval & Publication
  6. Publication (Only after approval)

What it can do on your machine

Read from SKILL.md and the folder at commit da3ca3c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • bash
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release Beta loads about 2k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 879 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Thank-you-Linus/Linus-Dashboard at commit da3ca3c, republished under its MIT licence (© Thank-you-Linus). 879 words, ~1,969 tokens.

Download SKILL.mdSave it as .claude/skills/release-beta/SKILL.md (or your agent's skills folder).
name
release-beta
description
Create a beta pre-release for community testing with intelligent version detection. Use when creating beta releases, publishing pre-releases, or preparing versions for community testing.

Create Beta Pre-Release

Create a BETA pre-release for community testing.

Current version: Check package.json for current version.

⚠️ CRITICAL TAG FORMAT RULE

NEVER use 'v' prefix in git tags!

  • ✅ CORRECT: 1.4.1-beta.1
  • ❌ WRONG: v1.4.1-beta.1

The GitHub workflows expect tags WITHOUT 'v' prefix. Using 'v' will cause workflow failures. All scripts (bump-version.sh, create-prerelease.sh) already create tags without 'v'. Never create tags manually - always use the scripts.

Intelligent Workflow

The workflow adapts automatically based on the current version:

First beta after stable release → AI analyzes commits and suggests version type (patch/minor/major) Incremental beta (beta.2 → beta.3) → Automatically increments without user validation

Phase 1: Version Detection & Analysis

Automatically detect release type:

  1. Detect release type:

    • Current version: 1.4.0 → First beta (requires AI analysis)
    • Current version: 1.4.0-beta.2 → Incremental beta (auto-increment to beta.3)

  2. For first beta after stable:

    • Run commit analysis: npm run analyze:commits
    • Analyze commit types (feat, fix, BREAKING CHANGE)
    • Count semantic changes
    • Determine version bump type (patch/minor/major)

  3. For incremental beta:

    • Skip analysis (already determined)
    • Auto-increment beta counter

Phase 2: Version Type Decision (First Beta Only)

AI Semantic Analysis Rules:

MAJOR (X.0.0):

  • Commits contain BREAKING CHANGE: in footer
  • Commits use ! after type (e.g., feat!:, fix!:)
  • API incompatible changes detected
  • Database schema changes
  • Major architecture refactoring

MINOR (X.Y.0):

  • New features detected (feat: commits)
  • Backward-compatible additions
  • New components, views, cards
  • Significant enhancements

PATCH (X.Y.Z):

  • Only bug fixes (fix: commits)
  • Documentation updates (docs:)
  • Small improvements/refactoring
  • Translation updates
  • Dependency updates

AMBIGUOUS:

  • Mixed signals (e.g., 5 feat + 1 BREAKING)
  • Unclear impact
  • → Ask user to decide manually
Present Validation Prompt:

Present detailed analysis with:

  • Current version
  • Proposed version
  • Commit breakdown (feat, fix, breaking, etc.)
  • AI reasoning with confidence level
  • Key commits (most impactful)
  • User decision options:
    • [1] APPROVE - Proceed with AI suggestion
    • [2] DOWNGRADE TO PATCH - Override AI
    • [3] UPGRADE TO MAJOR - Override AI
    • [4] VIEW COMMITS - Show full commit list
    • [5] CANCEL - Abort safely

Phase 3: Release Notes Generation & Editing

Automatically:

  1. Generate release notes (bash scripts/generate-release-notes.sh)
  2. AI-powered editing:
    • Remove noise (version bumps, merges, CI commits, deps updates)
    • Enhance features/fixes (bold title + detailed description)
    • Translate to French (same detail level)
    • Fill beta testing instructions
    • Remove TODO markers
  3. Format for GitHub (bash scripts/format-release-notes.sh)

Phase 4: Quality Validation (BLOCKING)

All must pass:

A. Release notes validation (scripts/validate-release-notes.sh)

  • Required sections EN/FR
  • No TODO
  • Beta testing filled
  • Bold features

B. Code quality (17 checks) (scripts/check-release-ready.sh)

  1. Git clean 2. Branch main 3. Up-to-date 4. Deps installed 5. Lint 6. Type-check 7. Build 8. Version consistency 9. No FIXME 10. CHANGELOG 11. manifest.json 12. hacs.json 13. No secrets 14. Python syntax 15. README 16. LICENSE 17. Smoke tests ready

C. Smoke tests (15 tests) (npm run test:smoke)

Phase 5: Final Approval & Publication

Present final approval with:

  • Version and bump type
  • Changes summary (features, bug fixes)
  • Beta testing checklist
  • Validation results
  • What happens if approved

User options:

  • [1] APPROVE - Publish beta release
  • [2] REQUEST CHANGES - Modify release notes
  • [3] VIEW FULL NOTES - See complete file
  • [4] CANCEL - Abort
Show full SKILL.md (395 more words)Show less

Phase 6: Publication (Only after approval)

For first beta with explicit version type:

  1. Bump version (bash scripts/bump-version.sh beta <patch|minor|major>)
    • Example: bash scripts/bump-version.sh beta minor → 1.5.0-beta.1
  2. Update release notes with final version
  3. Commit + tag (git commit + git tag)
  4. Push (git push && git push --tags)
  5. Report success with monitoring links

For incremental beta:

  1. Bump version (bash scripts/bump-version.sh beta)
    • Auto-increment: 1.5.0-beta.2 → 1.5.0-beta.3
  2. Update release notes with final version
  3. Commit + tag (git commit + git tag)
  4. Push (git push && git push --tags)
  5. Report success with monitoring links

GitHub Actions automatically:

  • Builds project
  • Runs smoke tests
  • Creates ZIP
  • Creates pre-release
  • Sends Discord notification to @Beta Tester
  • Cleans up RELEASE_NOTES.md

Quality Standards

Release notes: EN+FR equal quality, no TODO, detailed explanations, specific beta testing, user-focused, clean

Code: 17 checks passed, 15 smoke tests passed, lint+type-check passed, build succeeded

Version decision: AI analyzes commits semantically, presents detailed justification, user validates when needed

Options

Dry Run
--dry-run

Runs everything, creates commit+tag locally, STOPS before push. Nothing published. To undo: git reset HEAD~1 && git tag -d X.Y.Z-beta.N

Skip Approval (Final approval only)
--skip-approval

Shows summary but auto-approves final publication. Still requires version decision validation if first beta. ⚠️ Use with caution.

Logs

Every release logged to: .opencode/logs/release-beta-{timestamp}.log

Contains: timestamps, commit analysis, AI reasoning, user decisions, git hashes, URLs, duration

Common Errors

Validation fails → Fix issues, re-run command Smoke tests fail → Check npm run test:smoke, fix, re-run Build fails → Run npm run build, fix errors, re-run Push fails → git pull --rebase, re-run Tag exists → git tag -d X.Y.Z-beta.N or re-run (auto-increments) Ambiguous commits → AI asks you to decide manually between patch/minor/major

After beta testing:

  • ✅ Beta successful → Use release-stable skill (finalizes beta → stable)
  • 🐛 Issues found → Fix, then use release-beta skill again (increments beta.N automatically)
  • 🚨 Critical issue → Use release-rollback skill

Version Detection Logic Summary

Current VersionDetectionAI AnalysisUser ValidationResult
1.4.0 (stable)First beta✅ Yes✅ Required1.5.0-beta.1 (if MINOR)
1.4.0-beta.2Incremental❌ No❌ Not required1.4.0-beta.3
1.4.0-beta.5Incremental❌ No❌ Not required1.4.0-beta.6

Important

  • First beta: AI analyzes commits, presents detailed reasoning, requires your validation
  • Incremental beta: Automatic increment, no analysis, faster workflow
  • All validations are blocking (must pass)
  • Idempotent (safe to re-run)
  • Logs everything
  • Time: 5-10 min (first beta) or 3-5 min (incremental)

Scripts Used:

  • scripts/analyze-commits.sh - Commit analysis (first beta only)
  • scripts/bump-version.sh beta [patch|minor|major] - Version bumping
  • scripts/generate-release-notes.sh - Release notes generation
  • scripts/format-release-notes.sh - Formatting
  • scripts/validate-release-notes.sh - Validation
  • scripts/check-release-ready.sh - Code quality checks

© Thank-you-Linus, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/release-beta of Thank-you-Linus/Linus-Dashboard.

Open the folder on GitHubat commit da3ca3c

Compare with similar skills

Release Beta next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release Beta compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Beta this skillThank-you-Linus/Linus-Dashboard211—~2kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from Thank-you-Linus/Linus-Dashboard

  • Debug

    Thank-you-Linus/Linus-Dashboard

    Debug errors, bugs, and unexpected behavior systematically in Home Assistant integration.

    211 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Implement

    Thank-you-Linus/Linus-Dashboard

    Implement approved plans with precision and quality for Linus Dashboard Home Assistant integration.

    211 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Release Check

    Thank-you-Linus/Linus-Dashboard

    Check if project is ready for release with comprehensive pre-release validation.

    211 GitHub stars~637 tokensUpdated today
    Auto-check passed

  • Release Rollback

    Thank-you-Linus/Linus-Dashboard

    Rollback a failed release by deleting tags and reverting version changes.

    211 GitHub stars~789 tokensUpdated today
    Auto-check passed

  • Release Stable

    Thank-you-Linus/Linus-Dashboard

    Create a stable production release with intelligent detection (finalize beta or direct release).

    211 GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Review

    Thank-you-Linus/Linus-Dashboard

    Review code quality, security, and maintainability before committing.

    211 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

Categories

Questions about Release Beta

What does Release Beta do?

Create a beta pre-release for community testing with intelligent version detection. Release Beta is an agent skill from Thank-you-Linus/Linus-Dashboard. Create a beta pre-release for community testing with intelligent version detection.

When should I use Release Beta?

Release Beta fits situations like: creating beta releases; publishing pre-releases; preparing versions for community testing.

How do I install Release Beta in Claude Code?

Run `npx skills add Thank-you-Linus/Linus-Dashboard --skill release-beta -a claude-code`. Or copy the skill folder (.claude/skills/release-beta in Thank-you-Linus/Linus-Dashboard) into .claude/skills/release-beta in your project. Claude Code loads it when a task matches its description.

How do I install Release Beta in Codex?

Run `npx skills add Thank-you-Linus/Linus-Dashboard --skill release-beta -a codex`. Or copy the skill folder (.claude/skills/release-beta in Thank-you-Linus/Linus-Dashboard) into .agents/skills/release-beta in your project. Codex loads it when a task matches its description.

Can I use Release Beta in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Thank-you-Linus/Linus-Dashboard --skill release-beta -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-beta, .gemini/skills/release-beta, .github/skills/release-beta and .opencode/skills/release-beta in your project.

What does Release Beta need to run?

Going by SKILL.md and its folder, Release Beta needs the command-line tools its instructions call (git, bash and npm). Our summary lists: Python 3.

Does Release Beta access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release Beta safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release Beta use?

Release Beta is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Beta use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release Beta?

Skills that share tags, products or a category with Release Beta: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Beta?

Thank-you-Linus (a GitHub organization) maintains it in Thank-you-Linus/Linus-Dashboard, which has 211 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 10, 2026.

Source: Thank-you-Linus/Linus-Dashboard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.