release-check
Skill214 starsChanged 31 days agoMITView on GitHub
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.
- Installs packages
14 other projects use a version of this.
Adopted by
Most recently taken up by
- hhopke/intervals-icu-mcptheir own version, first seen Nov 8, 2026
- langchain-ai/design-agenttheir own version, first seen Oct 25, 2026
- phatysddev/skillstheir own version, first seen Oct 9, 2026
- ruby/rdoctheir own version, first seen Oct 8, 2026
- thoughtfulllc/gridlandtheir own version, first seen Oct 8, 2026
- samuelgursky/davinci-resolve-mcptheir own version, first seen Oct 8, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- samuelgursky/davinci-resolve-mcp★ 4ksame name
- ruby/rdoc★ 930same name
- langchain-ai/design-agent★ 596same name
- thoughtfulllc/gridland★ 363same name
- hhopke/intervals-icu-mcp★ 121same name
- lglucas/ai-dev-operating-system★ 12same name
- acailic/agent_debugger★ 9same name
- phatysddev/skills★ 8same name
- YorkWong1995/OPC-Harness★ 4same name
- broomva/lago★ 2same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .aidriven/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- debugSkill
- implementSkill
- release-betaSkill
- release-rollbackSkill
- release-stableSkill
- reviewSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run comprehensive pre-release validation checks.
- Distinctive: line 32
No FIXME/TODO comments
- Very specific: line 62
Run: npm run build to see detailed errors
- Very specific: line 67
Run: npm run lint to fix automatically
- Distinctive: line 78
All files should have same version:
- Distinctive: line 84
Run appropriate bump command to sync versions.
- Distinctive: line 110
Use release-beta skill - Pre-release for community testing (recommended)
- Distinctive: line 111
Use release-stable skill - Stable production release
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:checkWhat 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:smokeRuns 15 critical smoke tests to ensure basic functionality.
Release notes validation:
npm run release:validateValidates RELEASE_NOTES.md format and content.
If Checks Fail
Build Errors
- Run:
npm run buildto see detailed errors - Fix reported issues
- Re-run checks
Linting Errors
- Run:
npm run lintto fix automatically - Or:
npm run lint:checkto see issues - Fix any remaining manual issues
- Re-run checks
Type Errors
- Run:
npm run type-checkto 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:changelogMissing RELEASE_NOTES.md
npm run release:notesDependencies Out of Date
npm installAfter 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.