custom-git-commit

Automate conventional commits and primary-document synchronization for custom projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Custom project work often struggles with inconsistent commits and drift between primary documents and project workflows. This skill enforces a consistent conventional-commit standard while coordinating synchronization of primary documents when CLAUDE.md specifies a custom workflow.

Core Features & Use Cases

  • Enforces traditional conventional commits across custom project contexts, ensuring clear, reviewable history.
  • Synchronizes the primary document from CLAUDE.md whenever configured, using update-primary-doc and related rules.
  • Validates CLAUDE.md configuration (type: custom) and milestones, and routes to relevant sub-skills as needed.

Quick Start

Describe the changes you want to commit for a custom project, and I will handle the full workflow including primary document synchronization and a conventional commit.

Frequently Asked Questions about custom-git-commit

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

FAQPage Schema
How do I enforce conventional commits for a custom project workflow?

Enforcing conventional commits for a custom project requires validating the CLAUDE.md configuration type as custom and synchronizing primary documents. This skill automates that workflow, coordinating updates and validating milestones to ensure a clear, reviewable commit history.

How does primary document synchronization work with CLAUDE.md?

Primary document synchronization with CLAUDE.md works by routing to update-primary-doc rules whenever a custom workflow is configured. It coordinates document updates during the commit process, preserving primary document integrity through robust validation and user-confirmed commits.

Can I automate commit workflows without drifting from my custom CLAUDE.md configuration?

Automating commit workflows without drifting from a custom CLAUDE.md configuration is possible by validating the type: custom setting and required primary documents. The skill coordinates update-primary-doc and update-claude-md, handling milestones to prevent configuration drift.

What is the best way to manage milestones and primary document integrity during custom commits?

Managing milestones and primary document integrity during custom commits is best handled by automating user-confirmed commits with robust validation. This approach enforces conventional commit standards while coordinating primary document synchronization based on CLAUDE.md sync rules.

Do I need to manually update primary documents when making conventional commits?

Manual updates to primary documents during conventional commits are unnecessary when CLAUDE.md specifies optional sync rules. The skill coordinates update-primary-doc automatically, validating required documents and preserving integrity throughout the custom project commit workflow.