release

Automate the vercel-plugin release workflow with gates, version bump, artifacts, commit, and push.

Updated May 31, 2026
One-click install
npx skills add https://github.com/vinhnguyenn020325-cmd/dinzkorea --skill release-vinhnguyenn020325-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/vinhnguyenn020325-cmd/dinzkorea/tree/main/.test-vercel-plugin/.claude/skills/release
Command: npx skills add https://github.com/vinhnguyenn020325-cmd/dinzkorea --skill release-vinhnguyenn020325-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the release process for the vercel-plugin, including running gates, bumping version, generating artifacts, committing, and pushing, thereby streamlining the release workflow.

Core Features & Use Cases

  • End-to-End Release Automation: Handles pre-flight checks, version bumping, artifact generation, and deployment tasks.
  • Pre-flight Checks: Ensures typecheck, tests, and validation are passed before proceeding.
  • Version Bumping: Automatically determines and updates the version based on user input or default settings.
  • Artifact Generation: Rebuilds generated artifacts, such as compiled hooks and the skill manifest.
  • Deployment: Stages, commits, and pushes changes to the main branch.
  • Use Case: Use this Skill to execute the full release process when required to "release", "ship", "bump and push", or "cut a release".

Quick Start

Use the release skill to automatically perform the release workflow for the vercel-plugin.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate the release workflow for a vercel-plugin in CI/CD?▼

Automating the release workflow for a vercel-plugin in CI/CD involves running pre-flight gates, bumping versions, generating artifacts, and pushing commits sequentially. This skill orchestrates those steps automatically when triggered by commands like "ship" or "cut a release".

What pre-flight checks are needed before bumping a version and deploying a plugin?▼

Required pre-flight checks before bumping a version and deploying a plugin include passing typecheck, tests, and validation. These gates ensure the codebase is stable before the release automation proceeds with committing and pushing artifacts.

Can I automatically rebuild generated artifacts like compiled hooks during a deployment?▼

Yes, generated artifacts like compiled hooks and the skill manifest can be automatically rebuilt during a deployment. The release workflow includes an artifact generation step that regenerates these files before staging and committing changes.

What's the best way to cut a release and push version-controlled plugin updates?▼

The best way to cut a release and push version-controlled plugin updates is using an end-to-end release automation script. It determines version bumps, updates configurations, stages changes, commits, and pushes directly to the main branch.

Does release automation work without external dependencies for plugin management?▼

Yes, release automation works without external dependencies for plugin management. The workflow relies entirely on internal scripts to handle gates, version bumping, artifact generation, and deployment without requiring additional external packages.