release

Automate end-to-end release workflows for vercel-plugin with version bumps and Git operations.

246|42|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/vercel/vercel-plugin --skill release-vercel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/vercel/vercel-plugin/tree/main/.claude/skills/release
Command: npx skills add https://github.com/vercel/vercel-plugin --skill release-vercel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end release processes for vercel-plugin are error-prone and manual; this skill automates gates, version bumps, artifact generation, and Git operations to streamline releases.

Core Features & Use Cases

  • End-to-end release workflow: perform pre-flight checks, determine version bump, generate artifacts, commit, and push.
  • Version management: update .plugin/plugin.json to reflect the new release version.
  • Validation & safety: ensures manifest integrity and frontmatter validation as part of the release process.

Quick Start

Trigger the end-to-end release workflow by asking to release or bump and push; the skill will run pre-flight checks, bump the version if needed, rebuild artifacts, and push changes.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumps and Git pushes for vercel-plugin releases?

Release automation for vercel-plugin handles end-to-end workflows by orchestrating pre-flight checks, version determination, artifact generation, and Git operations. It automatically updates .plugin/plugin.json, rebuilds artifacts, and pushes changes to main or release branches.

What is the end-to-end release workflow for vercel-plugin?

The end-to-end release workflow coordinates pre-flight checks, version bumps, building artifacts, and committing changes. It validates YAML frontmatter and manifest integrity before updating .plugin/plugin.json and triggering a rebuild to push changes to release branches.

How do I validate manifest integrity and frontmatter before a release?

Manifest integrity and YAML frontmatter validation are orchestrated automatically as pre-flight checks during the release workflow. The process verifies .plugin/plugin.json and frontmatter compliance before proceeding with version determination and artifact generation.

Can I use this release automation for both main and release branches?

Yes, the release automation supports pushing changes to both main and release branches. After performing pre-flight checks, version bumps, and artifact generation, the workflow orchestrates Git operations to commit and push changes to the target branch.

Do I need any external dependencies to run the vercel-plugin release workflow?

No external dependencies are required to run the vercel-plugin release workflow. The automation orchestrates pre-flight checks, version determination, building, and Git operations internally without relying on additional components or external tools.