skills.rest
NachoOsella
NachoOsellaCOMMUNITY
Explore all skills by this author →
GitHub

git-release

Determine semantic versions from commits and create GitHub release drafts.

6|Updated Jan 6, 2026
Search Tags:#automation#git#changelog#release#semantic#tagging
One-click install
npx skills add https://github.com/NachoOsella/DotFiles-V4 --skill git-release-nachoosella
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-release
Source: https://github.com/NachoOsella/DotFiles-V4/tree/main/pi/.pi/agent/skills/git-release
Command: npx skills add https://github.com/NachoOsella/DotFiles-V4 --skill git-release-nachoosella

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

Streamlines release management by automatically generating changelogs, determining the next semantic version, and preparing GitHub releases from commit history.

Core Features & Use Cases

  • Semantic versioning: derives v-major, v-minor, or v-patch from conventional commits.
  • Changelog automation: builds a structured CHANGELOG from recent commits.
  • Release orchestration: tags the repo, pushes updates, and creates a GitHub release draft.
  • Use Case: teams adopting a repeatable release process can trigger a single command to prepare a release with notes and tags.

Quick Start

Run the release workflow to generate a changelog, tag the new version, and publish a GitHub release.

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 from git commits?▼

Automate semantic versioning by deriving the next version from conventional commits since the last tag, generating a structured changelog, and tagging the repository to streamline release management.

How does semantic release tagging determine the next version number?▼

Semantic release tagging calculates the next version by parsing commit history since the last tag, deriving v-major, v-minor, or v-patch based on conventional commit messages to determine the appropriate version bump.

Can I create a GitHub release draft with an automated changelog from commit history?▼

Yes, you can create a GitHub release draft populated with automated changelog notes generated from recent commits, which also reference linked pull requests for comprehensive release orchestration.

What is the best way to tag a repository and push the new version to the main branch?▼

The best way to tag and push a new version is to run a single release command that calculates the semantic version, tags the repository, and pushes the tag directly to the main branch.

Does this semantic release workflow require any external dependencies to run?▼

No, this semantic release workflow operates without external dependencies, using only its internal scripts and assets to calculate versions, build changelogs, and push tags to your repository.

When do I need to generate a changelog for a new release?▼

You need to generate a changelog when preparing a new release, as it builds a structured history from recent commits to provide clear release notes for teams adopting a repeatable release process.

Related Skills

Explore More Software Engineering Skills→
jonnymuirjonnymuir
1

Conventional Commits

Standardize git commit messages for automated semantic versioning and changelog generation.

Community
Basic
dotnetdotnet
209

ci-validation-gates

Validate semver, npm token types, and release events in GitHub Actions workflows.

Official
Advanced
sudocarlossudocarlos
4

git-workflow

Validate Git commit messages and branch naming against conventional commit standards.

Community
Intermediate
gittowergittower
413

release

Update changelog and version files from git history using semantic versioning.

Official
Advanced