commit

Generate conventional commit messages and PR titles for Release Please.

Updated Mar 21, 2021
One-click install
npx skills add https://github.com/TobiasGoetz/pibot --skill commit-tobiasgoetz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/TobiasGoetz/pibot/tree/main/.cursor/skills/commit
Command: npx skills add https://github.com/TobiasGoetz/pibot --skill commit-tobiasgoetz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing consistent commit messages and PR titles that align with Release Please can be error-prone and time-consuming, leading to inconsistent versioning and unclear release notes.

Core Features & Use Cases

  • Generates conventional commit messages with the proper type, scope (optional), and description.
  • Produces PR titles that match Release Please expectations to trigger correct version bumps.
  • Useful for daily Git workflows including commits, squashes, or naming release PRs across multiple repositories.

Quick Start

Tell me to format a message as feat(auth): add login flow.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for Release Please?

PR titles for Release Please must follow the conventional commit format with a valid type, optional scope, and imperative description. Generating matching PR titles ensures the automated release process triggers the correct version bumps.

What is the correct format for a conventional commit type and scope?

The conventional commit format includes a type, an optional scope in parentheses, and an imperative description, such as feat(auth): add login flow. This structure is required to ensure correct version bumps in release notes.

How do I squash commits while maintaining conventional commit standards?

You squash commits by generating a single conventional commit message that summarizes the combined changes using the correct type and optional scope. This preserves the structured format needed for Release Please to trigger correct version bumps.

Do I need a specific Git workflow to use conventional commits with Release Please?

No specific Git workflow is required. The process applies to daily Git workflows including standard commits, squashes, and naming release PRs across multiple repositories that use conventional commits.

Why does my Release Please release note show the wrong version bump?

Release Please may trigger the wrong version bump if commit messages and PR titles lack the correct conventional commit type, optional scope, or imperative description. Enforcing this format resolves inconsistent versioning and unclear release notes.