Automates the release workflow for the scratch-code extension.
Install
mkdir -p .claude/skills/release-vladimir-kotikov && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10224" && unzip -o skill.zip -d .claude/skills/release-vladimir-kotikov && rm skill.zipInstalls to .claude/skills/release-vladimir-kotikov
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Release the scratch-code VS Code extension. Use when: cutting a new release, bumping version, publishing, tagging. Covers version bump, changelog update, commit, and signed tag.Key capabilities
- →Bump version
- →Update changelog
- →Commit release changes
- →Create signed git tags
- →Publish release
How it works
It automates the versioning, changelog updates, and tagging process for the scratch-code extension.
Inputs & outputs
When to use release
- →Cut a new release version
- →Bump extension version
- →Update changelog for new features
- →Tag production releases
About this skill
Release scratch-code Extension
When to Use
Any time a new version needs to be published: after a feature batch, a bug fix, or a breaking change.
Determine Bump Type
Review commits since the last release (git log --oneline <last-tag>..HEAD):
| Changes | Bump |
|---|---|
| Breaking changes (renamed/removed tools, schema changes) | major |
| New features or tools | minor |
| Bug fixes, documentation, refactors | patch |
Procedure
1. Bump the version
npm version <major|minor|patch> --no-git-tag-version
This updates package.json and package-lock.json but does not create a
git tag (the signed tag is created separately in step 4).
2. Update CHANGELOG.md
Add a new entry at the top of CHANGELOG.md following the existing style:
## [<version>]
- <concise present-tense bullet describing what changed>
- <another bullet>
Style rules (match existing entries):
- Start bullets with a capital action verb: Add, Fix, Improve, Refactor, Remove
- One idea per bullet; no trailing period
- No implementation details — describe user-visible behaviour
- Keep each bullet to one line where possible
3. Commit and push
git add package.json package-lock.json CHANGELOG.md
git commit -m "<version>"
git push
The commit message is the bare version string, e.g. 0.8.0.
4. Create the signed release tag
git make-release --<major|minor|patch>
Use the same bump type as step 1. The script will print the commits
included and prompt: About to push tag vX.Y.Z, continue? Yy/[Nn] — confirm
with y. This generates a signed tag and pushes it to the remote, triggering
the publish workflow.
When not to use it
- →When no changes are ready
- →When versioning is not required
Limitations
- →Requires git environment
- →Follows specific bump types
How it compares
It integrates version bumping, changelog management, and signed tagging into a single release workflow.
Compared to similar skills
release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release (this skill) | 0 | 3mo | No flags | Beginner |
| gcp-cloud-run | 5 | 5mo | Review | Intermediate |
| flow-nexus-platform | 6 | 4mo | Review | Beginner |
| smithery-mcp-deployment | 8 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
gcp-cloud-run
aj-geddes
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
flow-nexus-platform
ruvnet
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
smithery-mcp-deployment
CaullenOmdahl
Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
netlify-deploy
openai
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.