skills.rest
VMAFx
VMAFxOFFICIAL
Explore all skills by this author →
WebsiteGitHub

prep-release

Dry-run release-please to preview version, changelog, and blockers.

3|1|Updated May 28, 2026
Search Tags:#changelog#versioning#github actions#release#release-please#sbom#sigstore
One-click install
npx skills add https://github.com/VMAFx/vmafx --skill prep-release-vmafx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prep-release
Source: https://github.com/VMAFx/vmafx/tree/main/.claude/skills/prep-release
Command: npx skills add https://github.com/VMAFx/vmafx --skill prep-release-vmafx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you validate an upcoming release before a release-please pull request is merged, so you can catch versioning mistakes, missing prerequisites, and supply-chain gaps early.

Core Features & Use Cases

  • Release Preview: Dry-run release-please locally to see the next proposed version, affected packages, and tag outcome.
  • Changelog Review: Inspect the changelog diff and compare the current version against the proposed bump.
  • Prerequisite Verification: Check GitHub authentication, cosign availability, OIDC permissions, SBOM tooling, and SLSA workflow readiness.
  • Use Case: A maintainer preparing a release can use this Skill to confirm the next version matches the expected scheme and to surface blockers before merge.

Quick Start

Use the prep-release skill to dry-run the next release, review the proposed changelog and version changes, and report any blockers or missing prerequisites.

Frequently Asked Questions about prep-release

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

FAQPage Schema
How do I validate a release-please pull request before merging?▼

To validate a release-please pull request before merging, you can dry-run release-please locally to preview the proposed version bump, affected packages, and tag outcome. This preflight check surfaces versioning mistakes and missing prerequisites early.

What is release preflight verification for GitHub actions?▼

Release preflight verification for GitHub actions is the process of dry-running release-please to surface the proposed changelog delta, version changes, and blocker list before a pull request is merged, ensuring supply-chain readiness.

How do I check supply-chain readiness for an upcoming GitHub release?▼

To check supply-chain readiness for an upcoming GitHub release, verify GitHub authentication, cosign availability, OIDC release permissions, and SBOM or SLSA tooling checks before merging the release-please pull request.

Can I preview the changelog diff and version bump before a release?▼

Yes, you can preview the changelog diff and version bump before a release by dry-running release-please. This allows you to inspect the changelog delta and compare the current version against the proposed bump.

Does preflighting a release require cosign and OIDC permissions?▼

Yes, preflighting a release requires modern cosign support and OIDC release permissions to verify supply-chain readiness. Authenticated GitHub access and SBOM or SLSA tooling checks are also required.

What blockers should I look for when preparing a release with release-please?▼

When preparing a release with release-please, look for blockers like missing GitHub authentication, absent cosign support, insufficient OIDC release permissions, and missing SBOM or SLSA tooling checks that prevent a successful merge.

Related Skills

Explore More Software Engineering Skills→
Arcanada-oneArcanada-one
11

release-verify

Verify Datarim GitHub Release artefacts via SHA-256, cosign, and SLSA L2 provenance.

Official
Advanced
andrewendlingerandrewendlinger
5

release

Orchestrate xmris releases from preflight checks to PyPI publication.

Community
Advanced
ivegamsftivegamsft

supply-chain-security

Automate artifact signing, SBOM generation, and SLSA provenance with GitHub Actions.

Community
Advanced
dwmkerrdwmkerr
23

release-please-development

Automates version bumps, changelog generation, and GitHub releases via Release Please.

Community
Intermediate