conventional-release

Write Conventional Commit PR titles and commit messages for automated releases.

2|Updated Apr 20, 2026

Search Tags:#changelog #semantic-release #semantic-versioning #conventional-commits #pr-title #squash-merge

Ready to run

npx skills add https://github.com/devantler-tech/agent-plugins --skill conventional-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-release
Source: https://github.com/devantler-tech/agent-plugins/tree/main/plugins/engineering-practices/skills/conventional-release
Command: npx skills add https://github.com/devantler-tech/agent-plugins --skill conventional-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you write PR titles and commit messages that drive automated releases without corrupting changelogs or producing the wrong version bump.

Core Features & Use Cases

Conventional Commit titles: Choose the right type, optional scope, and summary for squash-merged pull requests.
Version bump guidance: Decide whether a change should produce a major, minor, patch, or no release.
Release-tool alignment: Works with semantic-release, release-please, github-tag-action, and Changesets workflows.
Use Case: You are merging a bug fix into a repository that releases from the default branch; this skill helps you write the PR title so the patch release and changelog entry are generated correctly.

Quick Start

Write a single Conventional Commit PR title for my squash-merged change and tell me whether it produces a major, minor, patch, or no release.

Frequently Asked Questions about conventional-release

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

FAQPage Schema

How do I write a Conventional Commit PR title for a squash merge to trigger the right semantic version bump?▼

To trigger the correct semantic version bump with a squash merge, write a Conventional Commit PR title using the format type(scope): summary. Selecting the correct type, such as feat or fix, determines whether semantic-release generates a patch, minor, or major release.

Does semantic-release work with squash merge commit messages for automated changelog generation?▼

Yes, semantic-release works with squash merge commit messages for automated changelog generation. By configuring your repository to use the PR title as the commit message, semantic-release can parse the Conventional Commit format to automate versioning and update the changelog.

What is the correct Conventional Commit type for a breaking change in release-please?▼

The correct Conventional Commit type for a breaking change in release-please is adding the BREAKING CHANGE footer or using the ! symbol after the type. This signals release-please to generate a major semantic version bump and document the change in the changelog.

How do I choose between a feature and a refactor commit type for github-tag-action?▼

Choose the feat commit type for github-tag-action when adding new capabilities to produce a minor bump, and use refactor when restructuring code without changing behavior to prevent an unintended release. Correct selection ensures the semantic versioning pipeline only triggers when necessary.

Can I use Changesets with conventional commit PR titles for default-branch releases?▼

Yes, you can use Changesets with conventional commit PR titles. Aligning your PR titles with the type(scope): summary format ensures your default-branch release pipeline correctly interprets the changes and generates the appropriate version bump and changelog entry.

Why does my semantic-release pipeline skip a version bump after a squash merge?▼

Your semantic-release pipeline skips a version bump after a squash merge because the PR title lacks a valid Conventional Commit type. Using types like chore or test, or an improperly formatted summary, signals the pipeline to suppress the release.