release

Automate vercel-plugin releases by running gates, bumping versions, and pushing artifacts.

Updated May 31, 2026
One-click install
npx skills add https://github.com/ChristineTham/lp --skill release-christinetham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/ChristineTham/lp/tree/main/.agents/skills/release
Command: npx skills add https://github.com/ChristineTham/lp --skill release-christinetham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the release process for vercel-plugin by running gates, bumping versions, generating artifacts, and pushing changes, reducing manual release toil.

Core Features & Use Cases

  • Gate checks and validations in parallel
  • Determine and apply semantic version bumps in .plugin/plugin.json
  • Rebuild artifacts and push to repository

Quick Start

Run the end-to-end release workflow to cut a new vercel-plugin release when asked to perform a release or bump and push.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate a vercel-plugin release with version bumping and git push?

Automating a vercel-plugin release involves running pre-flight gates, bumping the semantic version in .plugin/plugin.json, rebuilding artifacts with bun run build, and pushing changes. This coordinates those steps automatically when a release is requested.

What is the single source of truth for versioning during a vercel-plugin release?

The version field in .plugin/plugin.json is the single source of truth for versioning. The release process reads and applies semantic version bumps directly to this file before regenerating artifacts and pushing updates.

Does this release automation process run gate checks in parallel?

Yes, the release automation runs gate checks and validations in parallel to streamline the process. It ensures all pre-flight checks complete successfully before proceeding with the version bump and git operations.

What's the best way to rebuild artifacts before pushing a vercel-plugin release?

The best way to rebuild artifacts is using the bun run build command. The release automation relies on this command to regenerate artifacts after the version bump and before pushing changes to the repository.

Can I trigger a release by asking to ship or bump and push?

Yes, you can trigger the release workflow using phrases like release, ship, bump and push, or cut a release. The automation recognizes these requests to coordinate gates, bump versions, and push artifacts.

What happens if pre-flight checks or git operations fail during a release?

The release automation enforces that pre-flight checks and git operations complete successfully. If any gate validation or git push fails, the release process halts to prevent incomplete or broken releases.