osx-commit

To detect a repository's git commit style, run an automated inspection script that scans Git history and configuration files like commitlint or .gitmojirc to identify whether Conventional, Angular, Gitmoji, or Classic standards are enforced.

Conventional Commits, Angular, and Gitmoji are distinct commit message standards. This Skill identifies the active standard by inspecting repository configuration and history, then applies the specific formatting rules, templates, and structural requirements for the detected commit style.

You can enforce consistent commit messages by detecting the repository's preferred standard from configuration files and guiding contributors with structured templates. This ensures every commit message complies with the detected Angular, Conventional, Gitmoji, or Classic style.

Yes, commitlint configuration files are inspected to determine the correct commit format. The detection script scans these files alongside Git history to establish whether Conventional, Angular, Gitmoji, or Classic style should be applied to new commit messages.

To write a compliant Gitmoji commit message, use the provided messaging templates and references after the repository's commit style is detected. This ensures your commit matches the required Gitmoji standard by applying the correct formatting and structure.

The detection script operates by inspecting Git history and reading configuration files to determine the applicable commit standard. It guides the creation of compliant commit messages without altering the existing repository configuration or commit history.