release

Automates semantic versioning releases with changelog generation and GitHub Release creation.

4|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/jey3dayo/pr-insights-labeler --skill release-jey3dayo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/jey3dayo/pr-insights-labeler/tree/main/.claude/skills/release
Command: npx skills add https://github.com/jey3dayo/pr-insights-labeler --skill release-jey3dayo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Releasing a new version of a GitHub Action involves many error-prone manual steps: bumping versions, running quality checks, generating changelogs, creating tags, updating floating major-version tags, and publishing GitHub Releases. This Skill automates the entire workflow so releases are consistent and nothing is forgotten. ## Core Features & Use Cases - Automated Release Workflow: Runs quality checks (lint, type-check, tests, build), bumps the version in package.json, updates CHANGELOG.md, and creates git commits and tags. - Changelog Generation: Builds release notes from Conventional Commits following the .github/RELEASE_TEMPLATE.md format, with automatic breaking-change detection and PR number extraction. - Major Version Tag Management: Maintains floating tags (v1, v2) and updates their GitHub Releases so users referencing @v1 always get the latest release. - Use Case: When you are ready to ship a bug fix, ask for a patch release; the Skill validates the working tree, runs all checks, tags v1.8.1, updates the v1 floating tag, and publishes the GitHub Release with standardized notes. ## Quick Start Create a patch release for this repository with full quality checks and a GitHub Release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I create a release with semantic versioning?▼

Run the release workflow and choose patch, minor, or major. The Skill updates package.json, regenerates CHANGELOG.md from Conventional Commits, creates the version tag, and publishes a GitHub Release with notes following the project template.

How to generate a changelog from Conventional Commits?▼

Changelogs are generated by classifying git log subjects between the previous tag and HEAD using the prefix-to-section mapping in .github/RELEASE_TEMPLATE.md. Commit prefixes like feat, fix, and refactor map to Added, Fixed, and Changed sections, with PR numbers extracted automatically.

Can I run the release script non-interactively?▼

The scripts/release.sh script requires an interactive terminal and accepts no arguments, so it fails in non-interactive sessions. In that case, follow the manual command-driven workflow documented in the Skill, which performs the same steps individually.

Why update the major version tag after a release?▼

GitHub Actions users reference floating tags like @v1 in workflows, so the v1 tag must be force-moved to the new release and its GitHub Release page updated. Skipping this leaves users on stale versions with misleading release notes.

What happens if the release push fails?▼

If the push fails, the commit and tags remain local. You can either push manually with git push origin main and the tag commands, or roll back with git reset --hard HEAD~1 and delete the local tags before retrying.