Release Maintainer
Undertone0809/rudder
A skill your agent uses when inspecting, preparing, executing, recovering, or verifying Rudder releases across npm, GitHub Releases, Desktop assets, tags, dist-tags, changelogs, Discord…
Check if project is ready for release with comprehensive pre-release validation.
$ npx skills add Thank-you-Linus/Linus-Dashboard --skill release-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Thank-you-Linus/Linus-Dashboard release-check --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-check .claude/skills/release-check && rm -rf skills-srcUse ~/.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/
Install the "release-check" agent skill from https://github.com/Thank-you-Linus/Linus-Dashboard/tree/main/.claude/skills/release-check into .claude/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Thank-you-Linus/Linus-Dashboard/tree/main/.claude/skills/release-checkType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Thank-you-Linus/Linus-Dashboard --skill release-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Thank-you-Linus/Linus-Dashboard release-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Thank-you-Linus/Linus-Dashboard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release-check .agents/skills/release-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-check" agent skill from https://github.com/Thank-you-Linus/Linus-Dashboard/tree/main/.claude/skills/release-check into .agents/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Thank-you-Linus/Linus-Dashboard --skill release-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Thank-you-Linus/Linus-Dashboard release-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Thank-you-Linus/Linus-Dashboard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release-check .cursor/skills/release-check && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-check" agent skill from https://github.com/Thank-you-Linus/Linus-Dashboard/tree/main/.claude/skills/release-check into .cursor/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Thank-you-Linus/Linus-Dashboard.git --path .claude/skills/release-check--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Thank-you-Linus/Linus-Dashboard --skill release-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Thank-you-Linus/Linus-Dashboard release-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Thank-you-Linus/Linus-Dashboard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release-check .gemini/skills/release-check && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-check" agent skill from https://github.com/Thank-you-Linus/Linus-Dashboard/tree/main/.claude/skills/release-check into .gemini/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Thank-you-Linus/Linus-Dashboard release-checkInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Thank-you-Linus/Linus-Dashboard --skill release-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Thank-you-Linus/Linus-Dashboard.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release-check .github/skills/release-check && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-check" agent skill from https://github.com/Thank-you-Linus/Linus-Dashboard/tree/main/.claude/skills/release-check into .github/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Thank-you-Linus/Linus-Dashboard --skill release-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Thank-you-Linus/Linus-Dashboard release-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Thank-you-Linus/Linus-Dashboard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release-check .opencode/skills/release-check && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-check" agent skill from https://github.com/Thank-you-Linus/Linus-Dashboard/tree/main/.claude/skills/release-check into .opencode/skills/release-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-check", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
release-checkCheck if project is ready for release with comprehensive pre-release validation.
Release Check is an agent skill from Thank-you-Linus/Linus-Dashboard. Check if project is ready for release with comprehensive pre-release validation. Use when verifying release readiness, running validation checks, or checking project quality before publishing.
Its SKILL.md is about 640 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, covering Changelog and release notes and Feature launches and release readiness. It works with npm. 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.
12 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit da3ca3c. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Release Check loads about 637 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 254 words of instructions outside code blocks.
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.
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.
The full file from Thank-you-Linus/Linus-Dashboard at commit da3ca3c, republished under its MIT licence (© Thank-you-Linus). 254 words, ~637 tokens.
.claude/skills/release-check/SKILL.md (or your agent's skills folder).Run comprehensive pre-release validation checks.
Current version: Check package.json for current version.
Execute the release check command:
npm run release:checkSmoke tests:
npm run test:smokeRuns 15 critical smoke tests to ensure basic functionality.
Release notes validation:
npm run release:validateValidates RELEASE_NOTES.md format and content.
npm run build to see detailed errorsnpm run lint to fix automaticallynpm run lint:check to see issuesnpm run type-check to see detailed errorsAll files should have same version:
Run appropriate bump command to sync versions.
npm run release:changelognpm run release:notesnpm installChoose release type based on changes:
© 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
Just SKILL.md in .claude/skills/release-check of Thank-you-Linus/Linus-Dashboard.
Open the folder on GitHubat commit da3ca3c
Release Check 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Check this skillThank-you-Linus/Linus-Dashboard | 211 | — | ~637 | Automated safety check: Pass | MIT | |
| Release MaintainerUndertone0809/rudder | 292 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Release Coherencemacalbert/envilder | 138 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Herdr Pre-Release Auditherdrdev/herdr | 43k | — | ~289 | Automated safety check: Pass | Apache-2.0 | |
| Megaphone ReleaseKuberwastaken/megaphone | 170 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Create Release Checklistsoftware-mansion/smelter | 734 | — | ~1.9k | Automated safety check: Notes | Custom licence |
Undertone0809/rudder
A skill your agent uses when inspecting, preparing, executing, recovering, or verifying Rudder releases across npm, GitHub Releases, Desktop assets, tags, dist-tags, changelogs, Discord…
macalbert/envilder
Unified release coherence workflow for any component (CLI, GHA, or SDK).
herdrdev/herdr
Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's…
Kuberwastaken/megaphone
Prepare, validate, publish, and verify Megaphone releases. An agent skill from Kuberwastaken/megaphone.
software-mansion/smelter
Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK.
OdradekAI/bundles-forge
A skill your agent uses when releasing a bundle-plugin, bumping versions, fixing version drift across manifests, setting up version sync infrastructure, updating CHANGELOG, publishing to…
Thank-you-Linus/Linus-Dashboard
Debug errors, bugs, and unexpected behavior systematically in Home Assistant integration.
Thank-you-Linus/Linus-Dashboard
Implement approved plans with precision and quality for Linus Dashboard Home Assistant integration.
Thank-you-Linus/Linus-Dashboard
Create a beta pre-release for community testing with intelligent version detection.
Thank-you-Linus/Linus-Dashboard
Rollback a failed release by deleting tags and reverting version changes.
Thank-you-Linus/Linus-Dashboard
Create a stable production release with intelligent detection (finalize beta or direct release).
Thank-you-Linus/Linus-Dashboard
Review code quality, security, and maintainability before committing.
Works with
Categories
Check if project is ready for release with comprehensive pre-release validation. Release Check is an agent skill from Thank-you-Linus/Linus-Dashboard. Check if project is ready for release with comprehensive pre-release validation.
Release Check fits situations like: verifying release readiness; running validation checks; checking project quality before publishing.
Run `npx skills add Thank-you-Linus/Linus-Dashboard --skill release-check -a claude-code`. Or copy the skill folder (.claude/skills/release-check in Thank-you-Linus/Linus-Dashboard) into .claude/skills/release-check in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Thank-you-Linus/Linus-Dashboard --skill release-check -a codex`. Or copy the skill folder (.claude/skills/release-check in Thank-you-Linus/Linus-Dashboard) into .agents/skills/release-check in your project. Codex loads it when a task matches its description.
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-check -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-check, .gemini/skills/release-check, .github/skills/release-check and .opencode/skills/release-check in your project.
Going by SKILL.md and its folder, Release Check needs the command-line tools its instructions call (npm). Our summary lists: Python 3; Node.js.
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Release Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 637 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Release Check: Release Maintainer (Undertone0809/rudder, 292 stars), Release Coherence (macalbert/envilder, 138 stars), Herdr Pre-Release Audit (herdrdev/herdr, 43k stars) and Megaphone Release (Kuberwastaken/megaphone, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.