commit

Generates scope-based commit messages with automatic language detection.

Updated Apr 24, 2026

Search Tags:#git #workflow #commits #scope #conventional-commits #language-detection

Ready to run

npx skills add https://github.com/bc05/codex-skills --skill commit-bc05

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/bc05/codex-skills/tree/main/commit
Command: npx skills add https://github.com/bc05/codex-skills --skill commit-bc05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps teams consistently structure and communicate Git changes by applying Conventional Commits, enforcing per-scope commits, and selecting the language of messages based on the repository history.

Core Features & Use Cases

Conventional Commits enforcement: ensures every commit follows the standard format.
Scope-based commits: splits changes into independent commits by domain or feature.
Language adaptation: detects whether the recent history is Portuguese or English and uses that language for messages.

Quick Start

Create a new commit with a clear scope, and let the tool inspect history to choose the appropriate language and format.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automate conventional commits with scope-based organization in Git?▼

To automate conventional commits with scope-based organization, the Skill analyzes your repository history to enforce the standard format and splits changes into independent commits by domain or feature.

How does language detection work for Git commit messages?▼

Language detection for Git commit messages works by analyzing recent repository history to infer whether Portuguese or English is used, then automatically adapting the generated commit message to match that language.

Can I split multi-team repository changes into per-scope commits?▼

Yes, you can split multi-team repository changes into per-scope commits. The Skill applies Conventional Commits to projects with multi-team histories, organizing changes into independent commits by domain or feature.

What is the best way to ensure my Git workflow follows Conventional Commits?▼

The best way to ensure your Git workflow follows Conventional Commits is to use an automated tool that inspects your repository history and outputs a ready-to-commit message enforcing the standard structure and appropriate scope.

Do I need a specific Git workflow to use scope-based conventional commits?▼

No specific Git workflow is required. The Skill applies to projects with multi-team histories and analyzes recent commit history to enforce the Conventional Commits structure and select the correct message language.