custom-git-commit

Generate conventional Git commits with CLAUDE.md-based validation and document sync.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams create clean, conventional Git commits for custom project types by enforcing project-type configuration, syncing primary documents, and validating changes before commit.

Core Features & Use Cases

  • Syncs the primary document based on CLAUDE.md configuration.
  • Validates staged changes using configured validators before committing.
  • Generates conventional commit messages in line with the Conventional Commits spec.
  • Supports milestones and metadata checks to align with project workflows.
  • Extends git-commit to handle type: custom project workflows.

Quick Start

Update CLAUDE.md with a type: custom configuration, stage your changes, and begin the commit workflow via the git-commit route.

Frequently Asked Questions about custom-git-commit

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

FAQPage Schema
How do I automate conventional commits for custom project types?

You can automate conventional commits by configuring CLAUDE.md with a type: custom declaration, staging your changes, and initiating the workflow to validate and sync primary documents before committing.

What is a custom project commit workflow in Git?

A custom project commit workflow enforces pre-commit checks, syncs primary documents based on CLAUDE.md configuration, and validates staged changes for specific project types like research or documentation.

Does the conventional commit workflow require a specific configuration file?

Yes, the workflow requires a CLAUDE.md file configured with type: custom settings to define validators, sync rules, and milestone checks before generating a conventional commit message.

How do I validate staged changes before creating a conventional commit?

Staged changes are validated using configured validators within the workflow, ensuring that all modifications meet project-specific rules and primary document sync requirements before the commit is finalized.

Can I sync a primary document automatically before a Git commit?

Yes, the workflow automatically syncs the primary document by reading sync rules from the CLAUDE.md configuration file prior to running pre-commit checks and generating the commit message.

Are there limitations to custom project commit workflows for conventional commits?

This workflow specifically applies to custom project types declaring type: custom in CLAUDE.md, meaning standard project types without this configuration will not trigger the extended sync and validation rules.