release

Automates versioned releases of vercel-plugin by running gates, bumping versions, and pushing commits.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/dsgalkar/dnyaneshwar_portfolio --skill release-dsgalkar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/dsgalkar/dnyaneshwar_portfolio/tree/main/.agents/plugins/vercel/.claude/skills/release
Command: npx skills add https://github.com/dsgalkar/dnyaneshwar_portfolio --skill release-dsgalkar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing a plugin involves many error-prone manual steps: running typechecks and tests, bumping the version, rebuilding artifacts, and crafting a consistent commit. This Skill orchestrates the entire release workflow for vercel-plugin so nothing is skipped. ## Core Features & Use Cases - Pre-flight Quality Gates: Runs typecheck, tests, and skill/manifest validation in parallel and stops the release if any gate fails. - Semver Version Management: Reads and bumps the version in .plugin/plugin.json (the single source of truth) with guidance on patch vs. minor vs. major. - Artifact Rebuild & Release Commit: Recompiles hooks via bun run build, regenerates the skill manifest, then stages, commits with the conventional ; bump to X.Y.Z message, and pushes. - Use Case: You finished adding a new hook to vercel-plugin and want to ship it. Invoke the release workflow to validate everything, bump the minor version, rebuild, and push to main in one guided flow. ## Quick Start Ask the assistant to release vercel-plugin with a patch version bump and push the result to main.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I release a new version of vercel-plugin?

Invoke the release workflow, which runs typecheck, tests, and validation gates, bumps the version in `.plugin/plugin.json`, rebuilds hooks and the skill manifest with `bun run build`, then commits and pushes with a `; bump to X.Y.Z` message.

How do I choose between patch, minor, and major version bumps?

Use patch for bug fixes, test or fixture updates, and docs; minor for new skills, hooks, or features; and major for breaking changes to the hook API or skill map. If unspecified, the workflow defaults to patch.

Where is the version number stored for vercel-plugin?

The version lives only in the `version` field of `.plugin/plugin.json`. There is no `package.json` version to keep in sync, making this file the single source of truth.

What happens if a pre-flight check fails during release?

The workflow stops immediately if typecheck, tests, or validation fails. You must fix the underlying issue and rerun the gates before the version bump, build, and commit steps proceed.

Can I amend a failed release commit instead of creating a new one?

No. If the pre-commit hook fails after re-running typecheck and recompiling hooks, fix the issue and create a new commit. Amending is explicitly disallowed to preserve release history.