git-commit

Create conventional commit messages following the Conventional Commits 1.0.0 specification.

1|5|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/mdproctor/claude-skills --skill git-commit-mdproctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/mdproctor/claude-skills/tree/main/git-commit
Command: npx skills add https://github.com/mdproctor/claude-skills --skill git-commit-mdproctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The commit history often becomes unclear and inconsistent. This Skill guides you to craft clean, conventional commit messages that adhere to the Conventional Commits 1.0.0 specification, improving traceability and reviewability.

Core Features & Use Cases

  • Standardized messages: Enforces subject lines in imperative mood, max 50 characters, no trailing period.
  • Safety checks: Requires explicit user confirmation before running a commit and blocks attribution unless requested.
  • Workflow routing: Determines project type from CLAUDE.md and routes to specialized skills or handles generically for standard repos.

Quick Start

Provide a conventional commit subject and optional body, then confirm to complete the commit.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I create conventional commit messages in git?

To create conventional commit messages, this Skill formats your git commits to the Conventional Commits 1.0.0 specification, enforcing imperative mood and a 50-character subject limit. You provide the subject and optional body, then confirm to execute the commit safely.

Why does my git commit history lack traceability and consistency?

Your git commit history lacks traceability when messages are unstructured. This Skill solves the problem by enforcing clean, conventional commits with consistent formatting rules like prohibiting trailing periods, which directly improves code reviewability.

Can I automate git commits without explicit user confirmation?

You cannot automate git commits without confirmation here, as this Skill enforces explicit user confirmation before running any commit. This safety check prevents accidental changes and requires your approval before finalizing the workflow.

Does this conventional commit workflow support project type routing?

This conventional commit workflow supports project type routing by reading CLAUDE.md to determine your configuration. It routes specialized project types to dedicated skills and handles standard repositories generically.

How do I prevent automated commit attribution in my git workflow?

To prevent automated commit attribution in your git workflow, this Skill blocks attribution by default unless explicitly requested. It ensures your commit messages remain clean and free of automated signatures.