release

Automate vercel-plugin releases with pre-flight checks, version bumps, and git operations.

Updated Dec 12, 2025
One-click install
npx skills add https://github.com/global-os/gproxy --skill release-global-os
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/global-os/gproxy/tree/main/.agents/skills/release
Command: npx skills add https://github.com/global-os/gproxy --skill release-global-os

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the release process for the vercel-plugin, handling gates, version bumping, artifact generation, and deployment. It's essential for automating software release workflows.

Core Features & Use Cases

  • End-to-End Release Automation: Automates steps like gates, version bumping, artifact generation, commit, and push.
  • Pre-flight Checks: Ensures typecheck, testing, and validation are passed before proceeding.
  • Version Bumping: Allows for specifying which semver component to bump and updates the version field in .plugin/plugin.json.
  • Rebuilding Artifacts: Regenerates hooks and the skill manifest for deployment.
  • Git Operations: Stages, commits, and pushes changes to the repository.
  • Use Case: It can be used during a CI/CD pipeline to automatically cut a release when new versions are deployed.

Quick Start

Run the release skill to automate the release process.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate the vercel-plugin release process in a CI/CD pipeline?

To automate the vercel-plugin release process in a CI/CD pipeline, you can run a skill that handles pre-flight checks, version bumping, artifact generation, and git operations. This streamlines deployment by automating the end-to-end release workflow.

What pre-flight checks are required before bumping the version in a vercel-plugin release?

Before bumping the version in a vercel-plugin release, pre-flight checks ensure that typecheck, testing, and validation are passed. These gates verify code stability before proceeding with artifact generation and deployment.

Can I specify which semver component to bump when automating vercel-plugin releases?

Yes, you can specify which semver component to bump during vercel-plugin release automation. The process updates the version field in the .plugin/plugin.json file according to the specified semver component before rebuilding artifacts.

Does the vercel-plugin release automation handle git commit and push operations?

Yes, vercel-plugin release automation handles git operations by staging, committing, and pushing changes to the repository. This ensures the version bump and rebuilt artifacts are deployed directly through the workflow.

When should I use an automated release workflow for vercel-plugin development?

You should use an automated release workflow for vercel-plugin development when you need to cut a release automatically during a CI/CD pipeline deployment. It streamlines gates, version bumping, and artifact generation without manual intervention.

What is the best way to regenerate hooks and the skill manifest for vercel-plugin deployment?

The best way to regenerate hooks and the skill manifest for vercel-plugin deployment is through the release automation process. It automatically rebuilds these artifacts after version bumping and before executing git operations.