trigger-prepare-release

Triggers the prepare-release GitHub Actions workflow with version, bump, channel, and base branch arguments.

1.6k|73|Updated Mar 13, 2025
One-click install
npx skills add https://github.com/UniClipboard/UniClipboard --skill trigger-prepare-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trigger-prepare-release
Source: https://github.com/UniClipboard/UniClipboard/tree/main/.agents/skills/trigger-prepare-release
Command: npx skills add https://github.com/UniClipboard/UniClipboard --skill trigger-prepare-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually dispatching the prepare-release workflow is error-prone: the version input silently overrides channel, positional arguments are ambiguous, and base_branch is easy to confuse with the workflow's --ref. This Skill parses arguments safely, explains the pitfalls, and confirms parameters before dispatching.

Core Features & Use Cases

  • Argument Parsing: Accepts key=value pairs or positional tokens, classifying semver strings as versions, bare words like alpha/rc as channels, and patch/minor/major as bump types.
  • Trap Avoidance: Detects the ambiguous case where a user supplies both a semver token and a channel word, and asks for clarification instead of silently ignoring the channel.
  • Base Branch Handling: Supports releasing from a release/vX.Y.Z branch for iterating prereleases whose commits are not yet merged to main, with pre-flight checks that the branch is pushed.
  • Use Case: You want to ship an alpha at an exact version. Invoke the skill with 0.9.0-alpha.1, confirm the resolved parameters, and it runs gh workflow run prepare-release.yml with the correct inputs, then reports the run URL.

Quick Start

Ask the assistant to trigger the prepare-release workflow for version 0.9.0-alpha.1 on the main branch and confirm the dispatched run.

Frequently Asked Questions about trigger-prepare-release

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

FAQPage Schema
How do I trigger a GitHub Actions workflow with inputs from the command line?

Use gh workflow run with the workflow file name, --repo, --ref for the workflow definition branch, and -f flags for each input. This skill runs gh workflow run prepare-release.yml with version, bump, channel, and base_branch inputs after confirming them with you.

How do I release an exact prerelease version like 0.9.0-alpha.1?

Pass the full version including the channel suffix as the version input, for example version=0.9.0-alpha.1. The channel input is ignored whenever version is set, so version=0.9.0 plus channel=alpha would incorrectly produce v0.9.0.

Can I base a GitHub release on a branch other than main?

Yes, set base_branch to a branch such as release/v0.14.1. The workflow checks out that branch and targets the PR at it, but the branch must be pushed to the remote first, and the version is computed from that branch's package.json.

Why does the workflow run name show the bump type instead of the version?

The run name is prepare-release-v${version || bump}, so when version is empty it displays the bump type like vpatch rather than the resolved version. Check the Determine version step log or the opened PR title, which is release: v<resolved-version>.

What is the difference between --ref and base_branch when dispatching a workflow?

The --ref flag selects which branch's copy of the workflow file to run and should stay main so input validation uses the default branch definition. The base_branch input controls which branch the release is checked out from and where the PR is targeted.