release

Generate a changelog, create a git tag, and publish a GitHub release.

1|Updated Feb 15, 2026

Search Tags:#automation #git #changelog #versioning #github #release

Ready to run

npx skills add https://github.com/fabis94/fabis-ralph-loop --skill release-fabis94

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/fabis94/fabis-ralph-loop/tree/main/.universal-ai-config/skills/release
Command: npx skills add https://github.com/fabis94/fabis-ralph-loop --skill release-fabis94

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of creating new software releases, ensuring consistency and saving valuable developer time.

Core Features & Use Cases

Automated Changelog Generation: Creates a human-readable changelog from commit history.
Version Management: Handles version bumping in package.json and git tag creation.
GitHub Release Publishing: Publishes releases to GitHub, optionally as drafts or prereleases.
Use Case: After merging a set of features and bug fixes, use this Skill to automatically prepare and publish a new versioned release to GitHub, complete with an updated changelog.

Quick Start

Use the release skill to create a new version 1.2.0 release.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate git release creation and changelog generation from commit history?▼

You can automate git release creation by generating a changelog from conventional commit history, bumping the semver version in package metadata, creating a git tag, and publishing a GitHub release.

How does automated changelog generation work with conventional commits?▼

Automated changelog generation parses conventional commit formatting from your git history to create a human-readable summary of features and fixes for the new release.

Can I publish a GitHub release as a draft or prerelease using automation?▼

Yes, you can publish a GitHub release as a draft or prerelease, handling version validation and package metadata checks before publishing via GitHub CLI or token authentication.

Do I need GitHub CLI or a token to authenticate automated GitHub releases?▼

You need either GitHub CLI or an authentication token to publish releases, allowing the automation to handle version validation, package metadata checks, and semver versioning securely.

What is the best way to handle semver versioning and package metadata checks before a release?▼

Handling semver versioning involves validating the new version against package metadata like package.json, ensuring correct version bumping before creating a git tag and publishing.