release-funstack

Automate version bumps, commits, and GitHub releases with generated notes.

88|4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/uhyo/funstack-static --skill release-funstack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-funstack
Source: https://github.com/uhyo/funstack-static/tree/main/.claude/skills/release-funstack
Command: npx skills add https://github.com/uhyo/funstack-static --skill release-funstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines releasing new versions of a package by automating version bumps, git commits, and GitHub releases with generated notes.

Core Features & Use Cases

  • Automate version bump, commit, and push for a new release.
  • Generate release notes from commit history and publish a GitHub release via gh CLI.
  • Handle patch, minor, and major version updates with user confirmation when needed.

Quick Start

Release a new version by instructing the assistant to bump the version and publish on GitHub.

Frequently Asked Questions about release-funstack

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

FAQPage Schema
How do I automate GitHub releases and version bumps for a static package?

Automating GitHub releases involves bumping the package version, creating a git commit and tag, and publishing via the GitHub CLI. It generates release notes automatically from your commit history to streamline the publishing process.

How are release notes generated from git commit history?

Release notes are generated by analyzing git commit history between tags. The GitHub CLI assembles these commits into a changelog, which is then attached to the newly published GitHub release.

Do I need the GitHub CLI installed to publish releases?

Yes, the GitHub CLI is required to publish releases and assemble the changelog. You also need repository access and the ability to modify the package.json file to complete the version bump workflow.

Can I choose between patch, minor, and major version updates?

Yes, the release workflow supports patch, minor, and major version updates. It handles the semantic version bump in the package.json file and may request user confirmation before proceeding with the release.

What is the best way to manage versioning for a static package before publishing?

The best way to manage versioning is to modify the static package.json file directly. Bumping the version triggers a git commit and tag, preparing the repository state for a subsequent GitHub release.