git-release

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

6|Updated Jan 21, 2026

Search Tags:#changelog #npm #github #release #semantic versioning #git tagging

Ready to run

npx skills add https://github.com/SPeeDoA1/everything-opencode --skill git-release-speedoa1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-release
Source: https://github.com/SPeeDoA1/everything-opencode/tree/main/.opencode/skills/core/git-release
Command: npx skills add https://github.com/SPeeDoA1/everything-opencode --skill git-release-speedoa1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the release process by automating version bumps, changelog generation, and tagging, reducing manual overhead and human error.

Core Features & Use Cases

Semantic versioning enforcement: automatically bump MAJOR, MINOR, or PATCH based on changes and commit messages.
Changelog generation: generates and aggregates changelogs using conventional-changelog or standard-version.
Release publishing: tags releases, pushes to remote, and can publish npm packages or create GitHub Releases.
Use Case: when preparing a new software release, trigger a consistent, auditable release workflow from a single command.

Quick Start

To start a release, bump the version, generate the changelog, create and push a git tag, then publish to npm or create a GitHub release using the GH CLI.

Frequently Asked Questions about git-release

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

FAQPage Schema

How do I automate semantic versioning and changelog generation for npm releases?▼

You can automate version bumps, generate aggregated changelogs, create git tags, and publish npm packages or GitHub Releases using a single consistent workflow command driven by conventional commits.

How does conventional changelog generation work with semantic versioning?▼

Semantic versioning analyzes conventional commit messages to determine whether to bump the MAJOR, MINOR, or PATCH version, while conventional-changelog aggregates those commit messages into an automated changelog.

Can I publish npm packages and create GitHub Releases from a single command?▼

Yes, the release workflow tags releases, pushes to the remote repository, and publishes to npm or creates GitHub Releases using the GitHub CLI, streamlining the entire publishing process.

Do I need conventional commits to automate my release workflow?▼

Yes, conventional commits are required because the semantic versioning mechanism parses commit messages to automatically determine the correct version bump and generate the changelog.

What is the best way to manage git tagging for software releases without manual errors?▼

The best way is to automate the release process end-to-end by enforcing semantic versioning and conventional commits, which automatically updates versions, generates changelogs, and handles git tagging.

Why does my semantic versioning bump fail to generate the correct changelog?▼

Semantic versioning and changelog generation fail when commit messages do not follow the conventional commits format, preventing the parser from accurately determining version bumps or aggregating changes.