smithery.ai

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.

First seen Apr 6, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,546 B
  • docs SUMMARY.md 213 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

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)

  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:

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](package.json)
  • [customcomponents/linusdashboard/manifest.json](customcomponents/linusdashboard/manifest.json)
  • [customcomponents/linusdashboard/const.py](customcomponents/linusdashboard/const.py)
  • [src/linus-strategy.ts](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

  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