skills.rest
MithrilMan
MithrilManCOMMUNITY
Explore all skills by this author →
𝕏@MithrilManGitHub

gh-release-package

Automate GitHub package releases by bumping package.json and publishing via the Release workflow.

Updated Mar 12, 2026
Search Tags:#automation#workflow#versioning#github#release#gh#package
One-click install
npx skills add https://github.com/MithrilMan/neomithril-ui --skill gh-release-package
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-release-package
Source: https://github.com/MithrilMan/neomithril-ui/tree/main/.codex/skills/gh-release-package
Command: npx skills add https://github.com/MithrilMan/neomithril-ui --skill gh-release-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual, error-prone process of releasing new package versions by automating version calculation, release notes generation, and pushing the release through GitHub's Release workflow.

Core Features & Use Cases

  • Accepts an explicit semver version (e.g., 0.2.0) or a bump keyword (patch, minor, major, prepatch, preminor, premajor, prerelease) to determine the target version.
  • Validates prerequisites, updates package.json without creating a local tag, generates release notes, and guards against duplicate releases.
  • Applies a release workflow that reads and prepares the release from the default branch and publishes via GitHub so teams can automate CI/CD and artifact distribution.

Quick Start

Provide a version (e.g., 0.2.0) or a bump keyword (patch, minor, major, prepatch, preminor, premajor, prerelease) to trigger a new release through the repository's GitHub Release workflow.

Frequently Asked Questions about gh-release-package

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

FAQPage Schema
How do I automate GitHub package releases for an npm project?▼

Automating GitHub package releases involves validating prerequisites, computing the target version, updating package.json, generating release notes, guarding against duplicates, and pushing the release through the GitHub Release workflow.

Can I trigger a GitHub release using a semver bump keyword like patch or minor?▼

Yes, you can trigger a GitHub release by providing a bump keyword like patch, minor, major, prepatch, preminor, premajor, or prerelease, which the workflow uses to compute and apply the target version to your package.

Does the GitHub release workflow support pnpm and yarn alongside npm?▼

The GitHub release workflow supports projects using npm, yarn, or pnpm that maintain a package.json file, computing the target version and applying the version bump across these package managers.

What is the safest way to publish a package version without creating a local git tag?▼

Safe package publishing without a local tag uses an automated workflow that reads and prepares the release from the default branch, updates package.json, guards against duplicate releases, and publishes via GitHub.

Why does my automated package release workflow need to guard against duplicate releases?▼

Guarding against duplicate releases prevents redundant version publishes by validating prerequisites and checking the computed target version against existing GitHub releases before updating package.json and pushing.

Related Skills

Explore More Software Engineering Skills→
1a35e11a35e1
2

release

Automate npm release workflows with version bumps, changelogs, and GitHub releases.

Community
Advanced
NSEvteevNSEvteev
31

post-release

Validate GitHub Release artifacts, notes, changelog, and deployment steps.

Community
Intermediate
masakinihirotamasakinihirota

release-workflow

Manage secure code releases to the main branch with validation and versioning.

Community
Advanced
SPeeDoA1SPeeDoA1
6

git-release

Automate version bumps, changelog generation, and git tagging for releases.

Community
Advanced