How do I install the Release Check skill?

Run npx skillmds add majiayu000/release-check 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 Release Check safe to use?

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

Which AI agents work with Release Check?

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 Release Check free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release Check?

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

Release Check by majiayu000 — Agent Skill

Name: Release Check
Rating: 4.2 (5 reviews)
Author: majiayu000

Release Check

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.

majiayu000 88a6cbd 2 files · 3.4 KB Updated Sep 9, 2026 567 repo stars

File contents

Pre-Release Validation Checks

Run comprehensive pre-release validation checks.

Current version: Check package.json for current version.

Running Validation Checks

Execute the release check command:

npm run release:check

What Will Be Checked (17 Validations)

Git status is clean
On correct branch (main/master)
Up to date with remote
RELEASE_NOTES.md exists
Dependencies installed
Linting passes
Type checking passes
Build succeeds
Version consistency across files
No FIXME/TODO comments
CHANGELOG.md exists
Manifest.json valid
HACS.json valid
No sensitive data
Python syntax valid
README files exist
LICENSE exists

Additional Pre-Release Checks

Smoke tests:

npm run test:smoke

Runs 15 critical smoke tests to ensure basic functionality.

Release notes validation:

npm run release:validate

Validates RELEASE_NOTES.md format and content.

If Checks Fail

Build Errors

Run: npm run build to see detailed errors
Fix reported issues
Re-run checks

Linting Errors

Run: npm run lint to fix automatically
Or: npm run lint:check to see issues
Fix any remaining manual issues
Re-run checks

Type Errors

Run: npm run type-check to see detailed errors
Fix type issues in TypeScript files
Re-run checks

Version Mismatch

All files should have same version:

package.json
custom_components/linus_dashboard/manifest.json
custom_components/linus_dashboard/const.py
src/linus-strategy.ts

Run appropriate bump command to sync versions.

Quick Fixes

Missing CHANGELOG.md

npm run release:changelog

Missing RELEASE_NOTES.md

npm run release:notes

Dependencies Out of Date

npm install

After All Checks Pass

Choose release type based on changes:

Use release-beta skill - Pre-release for community testing (recommended)
Use release-stable skill - Stable production release

Workflow

Run validation checks
Fix any reported issues
Run smoke tests
Validate release notes
Proceed with release if all checks pass

---name: release-checkdescription: 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.--- # Pre-Release Validation Checks Run comprehensive pre-release validation checks. Current version: Check `package.json` for current version. ## Running Validation Checks Execute the release check command: ```bash npm run release:check ``` --- ## What Will Be Checked (17 Validations) 1. Git status is clean 2. On correct branch (main/master) 3. Up to date with remote 4. RELEASE_NOTES.md exists 5. Dependencies installed 6. Linting passes 7. Type checking passes 8. Build succeeds 9. Version consistency across files 10. No FIXME/TODO comments 11. CHANGELOG.md exists 12. Manifest.json valid 13. HACS.json valid 14. No sensitive data 15. Python syntax valid 16. README files exist 17. LICENSE exists --- ## Additional Pre-Release Checks **Smoke tests:** ```bash npm run test:smoke ``` Runs 15 critical smoke tests to ensure basic functionality. **Release notes validation:** ```bash npm run release:validate ``` Validates RELEASE_NOTES.md format and content. --- ## If Checks Fail ### Build Errors - Run: `npm run build` to see detailed errors - Fix reported issues - Re-run checks ### Linting Errors - Run: `npm run lint` to fix automatically - Or: `npm run lint:check` to see issues - Fix any remaining manual issues - Re-run checks ### Type Errors - Run: `npm run type-check` to see detailed errors - Fix type issues in TypeScript files - Re-run checks ### Version Mismatch All files should have same version: - [package.json](package.json) - [custom_components/linus_dashboard/manifest.json](custom_components/linus_dashboard/manifest.json) - [custom_components/linus_dashboard/const.py](custom_components/linus_dashboard/const.py) - [src/linus-strategy.ts](src/linus-strategy.ts) Run appropriate bump command to sync versions. --- ## Quick Fixes ### Missing CHANGELOG.md ```bash npm run release:changelog ``` ### Missing RELEASE_NOTES.md ```bash npm run release:notes ``` ### Dependencies Out of Date ```bash npm install ``` --- ## After All Checks Pass Choose release type based on changes: - Use release-beta skill - Pre-release for community testing (recommended) - Use release-stable skill - Stable production release --- ## Workflow 1. Run validation checks 2. Fix any reported issues 3. Run smoke tests 4. Validate release notes 5. Proceed with release if all checks pass

Frequently asked questions