release-please

Automate semantic versioning, changelog generation, and GitHub releases from conventional commits.

1|Updated Jul 22, 2026

Search Tags:#automation #changelog #versioning #github #release #ci-cd

Ready to run

npx skills add https://github.com/wyattjoh/skills --skill release-please-wyattjoh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-please
Source: https://github.com/wyattjoh/skills/tree/main/skills/release-please
Command: npx skills add https://github.com/wyattjoh/skills --skill release-please-wyattjoh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the manual overhead of tracking version bumps, generating changelogs, and managing GitHub releases by automating the entire release lifecycle based on conventional commits.

Core Features & Use Cases

Automated Versioning: Automatically calculates semantic version bumps based on commit history (feat, fix, breaking changes).
Changelog Generation: Maintains an up-to-date CHANGELOG.md file that reflects all changes since the last release.
Release Orchestration: Handles GitHub release creation, tag management, and optional downstream publishing workflows in a single, unified pipeline.

Quick Start

Configure the release-please skill in your repository to automatically detect your project type and generate a release pull request on your next commit.

Frequently Asked Questions about release-please

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

FAQPage Schema

How do I automate semantic versioning and changelog generation based on commits?▼

Automate semantic versioning and changelog generation by parsing conventional commit history to calculate version bumps and maintain an up-to-date CHANGELOG.md file. This eliminates manual overhead by automatically detecting project types and generating release pull requests.

How does conventional commit parsing determine semantic version bumps?▼

Conventional commit parsing determines semantic version bumps by mapping commit message prefixes like feat, fix, and breaking changes to corresponding major, minor, or patch version increments for your GitHub releases.

Can I use release automation for monorepos and multi-stage publishing pipelines?▼

Yes, you can automate releases for monorepos and multi-stage publishing pipelines. The automation handles complex workflows including binary artifact distribution and unified downstream publishing orchestration.

Do I need GitHub Actions to manage automated releases and tag management?▼

Yes, GitHub Actions integration is required to orchestrate automated release creation, tag management, and downstream publishing workflows within a unified CI/CD pipeline.

What happens if my project does not follow conventional commit standards?▼

Without conventional commit standards, automated version calculation cannot accurately determine semantic version bumps or generate accurate changelogs. Strict adherence to conventional commit message formatting is required for the release lifecycle to function.