Agent skill · software engineering · aiskillstore
release
Create a new version release with git tag and GitHub Release. Use when user asks to release, publish, create a new version, or ship a release. (project)
Why this skill is useful
Adds a complete executable script for version release management in a monorepo setup, including tagging and GitHub Release creation.
What it needs
Requires git, npm installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Release Skill Create a new version release using prefixed tag-based workflow for monorepo plugins. When to Use User explicitly asks to "release" or "create a release" User asks to "publish" or "ship" a new version User asks to "tag" a version User says "let's release v0.2.0" or similar Plugin Identification This is a monorepo with multiple plugins. First, identify which plugin to release: Plugin Version File Tag Format Example -------- ------------- ------------ --------- Stash Downloader plugins/stash-downloader/package.json downloader-vX.Y.Z downloader-v0.5.2 Stash Browser plugins/stash-browser/package.json browser-vX.Y.Z browser-v0.1.0 If the user doesn't specify, ask which plugin to release. If both changed, release each separately. Pre-Release Checklist Before creating a release, verify: 1. On dev branch: git branch --show-current 2. No uncommitted changes: git status 3. Type-check passes: npm run type-check 4. Lint passes: npm run lint 5. Tests pass: npm test -- --run 6. Build succeeds: npm run build Release Process (Tag-Based) Step 1: Determine Version Bump 1. Check current version: Read the plugin's package.json version field 2. Review commits since last tag: git log $(git describe --tags --match "downloader-v" --abbrev=0)..HEAD --oneline (or browser-v for Browser) 3. Determine bump type: Commit Types Bump Example -------------- ------ --------- Breaking changes (feat!:, BREAKING CHANGE) MAJOR 0.1.0 → 1.0.0 New features (feat:) MINOR 0.1.0 → 0.2.0 Bug fixes, patches (fix:, docs:, chore:) PATCH 0.1.0 → 0.1.1 Step 2: Merge dev to main and Release For Stash Downloader: For Stash Browser: Step 3: Wait and Sync Dev ⚠️ CRITICAL: Do NOT push to dev immediately! GitHub Pages uses a concurrency group. If you push to dev before the stable workflow finishes, the stable deploy gets CANCELLED. What Happens After Tag Push GitHub Actions automatically: 1. Runs CI (type-check, lint, tests) 2. Builds the plugin 3. Updates GitHub Pages (Stash plugin index) 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/release