commit

Generate conventional git commit messages with type, scope, and body.

4|1|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/dylangolow/claude-starter --skill commit-dylangolow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/dylangolow/claude-starter/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/dylangolow/claude-starter --skill commit-dylangolow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers maintain a clean, standardized git history by automatically guiding and generating conventional commit messages. It reduces guesswork and saves review time by ensuring commits follow the widely adopted conventional commit format.

Core Features & Use Cases

  • Conventional Commit Formatting: Automatically generate commit messages that adhere to the conventional commits specification.
  • Guided Staging: Assist in grouping related changes into coherent commits to improve history readability.
  • Body & Rationale Suggestions: Provide descriptive bodies that explain the "why" behind changes, aiding future maintenance and reviews.

Quick Start

Stage changes with git add, then ask Claude to commit using a conventional message, for example: "commit this change with type feat and scope authentication"

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create conventional git commits automatically?

Conventional commits are a standardized format for git messages that improves readability and automates changelog generation. Stage your changes with git add, then request a commit with a type (feat, fix, etc.) and scope. The Skill generates messages following type(scope): description format with the first line under 72 characters.

What is the conventional commits specification and why should I use it?

Conventional commits is a specification that standardizes commit message structure as type(scope): description, making git history readable and enabling automated versioning and changelog generation. It reduces review time and maintains a clean version-control history across your workflow.

How do I group related changes into a single commit?

Guided staging helps you organize related file changes into coherent commits. Stage files together with git add, then request a commit specifying the type and scope. The Skill groups related modifications while automatically skipping secrets, creating a logical, reviewable change set.

Can I include a commit body explaining why changes were made?

Yes. For complex changes, the Skill generates optional commit bodies that explain the rationale and context behind modifications. This improves future maintenance and code review by documenting the reasoning, not just the what.

Does this work with bash automation workflows?

Yes. The Skill integrates into bash-based automation and version-control workflows. Stage changes and invoke conventional commit generation as part of your workflow automation to enforce standardized messages across all commits.

What happens to sensitive data when committing?

The Skill automatically skips secrets during staging and commit generation, preventing credential leaks into your git history. Related changes are grouped while security-sensitive files are excluded from the commit.