commit

Name: commit
Availability: InStock
Author: bswrundquist

Generate Git commit messages following the Conventional Commits specification.

Updated Mar 9, 2026

Search Tags:#git #developer tools #version control #commit #conventional commits #code history

Ready to run

npx skills add https://github.com/bswrundquist/devtools --skill commit-bswrundquist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/bswrundquist/devtools/tree/main/src/devtools/templates/claude/user/.claude/skills/commit
Command: npx skills add https://github.com/bswrundquist/devtools --skill commit-bswrundquist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create clear, consistent, and informative Git commit messages, improving code history readability and automation.

Core Features & Use Cases

Conventional Commits: Adheres to the Conventional Commits specification for structured commit messages.
Logical Grouping: Guides the process of splitting changes into multiple, distinct commits.
Use Case: After implementing a new feature and fixing a related bug, use this Skill to create two separate commits: one for the feature (feat) and one for the bug fix (fix), each with a descriptive message.

Quick Start

Use the commit skill to create a new commit with the message "feat(auth): implement user login endpoint".

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate Git commit messages following the Conventional Commits specification?▼

To generate Git commit messages following the Conventional Commits specification, you can use this Skill to analyze your staged changes and output structured messages with specified commit types, scopes, and body formatting rules.

What is the best way to split mixed code changes into distinct logical Git commits?▼

The best way to split mixed code changes into distinct logical Git commits is to use this Skill, which guides the process of separating features and bug fixes into multiple commits with descriptive conventional messages.

Do I need Git CLI to analyze code diffs for automated changelog generation?▼

Yes, you need Git CLI installed because this Skill requires it to perform status and diff analysis on your repository, ensuring the resulting commit messages accurately reflect structured code changes for automated changelog generation.

Can I use Conventional Commits for semantic versioning in my software development workflow?▼

Yes, you can use Conventional Commits for semantic versioning in your software development workflow, as this Skill applies the specification to ensure clear commit history that directly supports automated semantic versioning and changelog generation.

How does logical grouping improve code history readability when committing features and fixes?▼

Logical grouping improves code history readability by separating unrelated changes into individual commits, such as creating a 'feat' commit for a new feature and a 'fix' commit for a related bug fix, each with its own descriptive message.

What are the limitations of automating structured commit messages for version control?▼

A limitation of automating structured commit messages is that the Skill requires Git CLI for status and diff analysis and strict adherence to specified commit types, scopes, and body formatting rules to function correctly within your version control workflow.