skills.rest
irwins
irwinsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-conventional-commit

Generate conventional commit messages and PR templates from summary, files, or diff.

Updated Feb 2, 2026
Search Tags:#automation#git#diff#code-review#conventional-commits#commit-messages#pr-templates
One-click install
npx skills add https://github.com/irwins/platform-agent-kit --skill git-conventional-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-conventional-commit
Source: https://github.com/irwins/platform-agent-kit/tree/main/.github/skills/git-conventional-commit
Command: npx skills add https://github.com/irwins/platform-agent-kit --skill git-conventional-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill standardizes commit messaging by generating conventional commit messages and PR templates in line with the Conventional Commits specification, reducing history drift and review overhead.

Core Features & Use Cases

  • Commit message generation: Produce commit titles and bodies that conform to the Conventional Commits format.
  • PR template suggestions: Create consistent PR titles and descriptions suitable for code reviews.
  • Use Case: When preparing a set of changes for a release, generate properly formatted commit entries and a PR description to accompany the changes.

Quick Start

Use the git-conventional-commit skill by providing a summary and optional files or diff; it outputs commit_title, commit_body, commit_footers, pr_title, and pr_description.

Frequently Asked Questions about git-conventional-commit

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

FAQPage Schema
How do I generate conventional commit messages from a git diff?▼

You generate conventional commit messages by providing a summary and optional files or diff. The skill outputs standardized commit titles, bodies, footers, and PR descriptions conforming to the Conventional Commits specification.

What is the Conventional Commits specification and when do I need it for code review?▼

The Conventional Commits specification standardizes commit messaging and PR templates to reduce review overhead. You need it when preparing changes for a release to ensure consistent history and properly formatted PR descriptions.

Can I include breaking changes and scope in my generated PR templates?▼

Yes, you can include breaking changes and scope as inputs. The skill processes these parameters to generate properly formatted PR titles, descriptions, commit titles, bodies, and footers that reflect the changes accurately.

Does this commit message generator work without external dependencies?▼

Yes, the commit message generator works without external dependencies. It uses internal scripts to process your summary, files, diff, scope, and breaking changes into standardized commit messages and PR templates.

What is the best way to standardize commit messages for a new release?▼

The best way to standardize commit messages for a release is to generate conventional commits and PR templates. This standardizes entries to the specification format, producing consistent titles, bodies, footers, and PR descriptions.

Related Skills

Explore More Software Engineering Skills→
accolveraccolver
4

git-commit-helper

Generate conventional commit messages from staged git changes.

Community
Intermediate
TobiasGoetzTobiasGoetz

commit

Generate conventional commit messages and PR titles for Release Please.

Community
Intermediate
Kevin-Liu-01Kevin-Liu-01
16

pr

Create pull requests with the Dedalus template and git state.

Community
Intermediate
Fandry96Fandry96
27

git-pushing

Stage changes, generate conventional commits, and push to a remote Git repository.

Community
Intermediate