git-commit

Generate conventional commit messages routed by project type.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers create clean, conventional Git commits following the Conventional Commits 1.0.0 specification, ensuring consistent messaging and enabling automated routing to specialized workflows based on project type.

Core Features & Use Cases

  • Route commits by project type using CLAUDE.md (java, custom, skills, generic)
  • Validate staged SKILL.md in skills repos using the skill-validation.md workflow
  • Generate conventional commit messages that describe WHAT changed and WHY, not HOW
  • Auto-trigger documentation and CLAUDE.md synchronization when relevant (update-claude-md, readme-sync)

Quick Start

Describe the changes you made and I will generate a conventional commit message and route you to the correct workflow.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write conventional commit messages for different project types?

Conventional commit messages are generated by converting your input into a standardized format aligned with your project context and routing rules. This ensures consistent messaging across Java projects, skills repos, custom docs, and generic worktrees.

How does CLAUDE.md routing work for git commits?

CLAUDE.md routing directs your conventional commit workflow based on project type, such as java, custom, skills, or generic. It validates staged SKILL.md files in skills repos and triggers documentation synchronization when relevant.

What is the best way to automate conventional commits with subject length limits and breaking change footers?

Automating conventional commits involves applying strict subject length limits, optional scope, and optional breaking-change footers to your messages. This enforces structural requirements and ensures compliance with the Conventional Commits 1.0.0 specification.

Can I use conventional commits to trigger documentation and CLAUDE.md synchronization?

Yes, conventional commits can auto-trigger documentation and CLAUDE.md synchronization through update-claude-md and readme-sync workflows. This happens automatically when the routing rules detect relevant changes in your project context.

Does this conventional commit workflow validate SKILL.md files in skills repos?

Yes, the workflow validates staged SKILL.md files in skills repos using the skill-validation.md workflow. This ensures your commits meet structural requirements and project-specific routing rules before finalizing.

Why do my conventional commit messages fail validation in a multi-project worktree?

Commit validation fails when messages do not adhere to strict subject length limits, optional scope formatting, or breaking-change footer requirements. The workflow validates SKILL.md presence and applies CLAUDE.md-driven routing to ensure compliance across project types.