Agent skill · software engineering · aiskillstore
blocklet-updater
Creates a new release for a blocklet project by bumping version, building, and bundling. Use when asked to "create a new release", "bump and bundle", or "update blocklet version".
Why this skill is useful
Adds an executable script for automating version bumps and CHANGELOG updates in blocklet projects, which the AI cannot generate on its own.
What it needs
Requires jq, pnpm installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Blocklet Updater Bumps a blocklet project version and creates a release bundle. Workflow 1. Version Bump (Smart Detection) Check for project-specific version update scripts before falling back to blocklet version patch. 1.1 Detect Version Update Method Check the following in priority order and use the first match: Priority Detection Command ---------- ----------- --------- 1 Makefile has bump-version target make bump-version 2 package.json has bump-version script pnpm run bump-version 3 package.json has version script pnpm run version 4 lerna.json exists lerna version patch --yes 5 None of the above blocklet version patch (fallback) Detection commands: 1.2 Execute Version Bump Run the detected command: Important: Project-specific scripts (like make bump-version) often: Update version file Auto-generate CHANGELOG.md entries Update multiple package versions in monorepos Call additional tooling scripts If fails → EXIT with error output. 1.3 Update CHANGELOG (If Exists) After version bump, verify and fix CHANGELOG.md if needed. 1.3.1 Get Actual Version First, get the actual version that was set (from blocklet.yml or package.json): 1.3.2 Find CHANGELOG Location 1.3.3 Validate CHANGELOG Entry For each CHANGELOG.md found, check if the latest entry matches the actual version: 1.3.4 Fix Version Mismatch If CHANGELOG version doesn't match actual version, fix it: 1. If CHANGELOG has a newer entry with wrong version (e.g., script partially ran): Replace the wrong version number with the correct one 2. If CHANGELOG has no entry for the new version: Add a new entry at the top 1.3.5 Check Entry Content After fixing version, check if the entry has content: 1.3.6 Generate Content for Empty Entry If entry is empty, generate content based on: 1. Git commits since last version tag: 2. Categorize by commit type (feat, fix, chore, etc.): 3. If no meaningful commits found, use AskUserQuestion to ask user for changelog content. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/blocklet-updater