commit

Create conventional commits with Co-Authored-By trailers for multi-service repositories.

21|4|Updated Jan 8, 2026

Search Tags:#git #commit #version-control #conventional-commits #submodules #change-management #multi-service

Ready to run

npx skills add https://github.com/JotJunior/claude-ai-tips --skill commit-jotjunior

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/JotJunior/claude-ai-tips/tree/main/language-related/go/skills/commit
Command: npx skills add https://github.com/JotJunior/claude-ai-tips --skill commit-jotjunior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Committing changes in large, multi-service repositories is error-prone without a consistent convention. This skill automates creating conventional commits, ensuring clear, standardized messages across services and submodules.

Core Features & Use Cases

Conventional commits formatting for features, fixes, docs, chore, and more.
Submodule and multi-service awareness to describe cross-cut changes in a single commit.
Safeguards to avoid committing secrets and to guide file selection when needed.

Quick Start

Run the commit helper to generate a conventional commit for the current changes.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I create conventional commits for a multi-service repository?▼

To create conventional commits across multiple services, the skill gathers context using git status, diffs, and logs, then enforces conventional commit formatting for staged and unstaged changes while respecting project conventions.

What is the best way to handle git commits across submodules and multiple services?▼

Handling git commits across submodules and multiple services requires multi-service awareness to describe cross-cut changes in a single commit. The process applies conventional commits formatting to features, fixes, docs, and chores, ensuring clear, standardized messages across all included services.

Can I automate conventional commit messages for both staged and unstaged changes?▼

Yes, automating conventional commit messages applies to scenarios involving both staged and unstaged changes. The system gathers context through git status and diffs, enforces the Conventional Commits format, and guides staged file selection before finalizing the commit message.

Does this conventional commit tool include safeguards against committing secrets?▼

Yes, this conventional commit tool includes safeguards to avoid committing secrets and guides file selection when needed. It ensures consistent, standardized messages across services and submodules while preventing accidental exposure of sensitive information during the commit process.

When do I need conventional commits in version control for large projects?▼

You need conventional commits in version control for large projects when committing changes across multiple services becomes error-prone without a consistent convention. Automating this process ensures clear, standardized messages that describe cross-cut changes across services and submodules.