Enforce Conventional Commits formatting for Git commit messages.
npx skills add https://github.com/niconiahi/ethernauta --skill git-niconiahi
Please help me install this Agent Skill. Skill: git Source: https://github.com/niconiahi/ethernauta/tree/main/.claude/skills/git Command: npx skills add https://github.com/niconiahi/ethernauta --skill git-niconiahi
It prevents inconsistent or vague Git commit messages by enforcing a predictable Conventional Commits format, scope usage rules, and strict one-line formatting.
type(scope): description (or type: description when scope is omitted).skill scope for changes to skill files.Co-Authored-By.Use the git skill whenever you create a commit, and format the message as type(scope): description in a single lowercase line with no period.
High-intent search queries and answers about installing and using this skill.
Conventional commit messages for CI and tooling changes use the format `type(scope): description` in a single lowercase line. You select the `ci` type and provide a domain-based scope to ensure project history consistency.
The correct format for a lowercase conventional commit is `type(scope): description`. The message must be a single line under 72 characters with no trailing period, ensuring predictable and unambiguous project history.
Commit messages for feature work and bug fixes require selecting the `feat` or `fix` type. You format the message as `type(scope): description` in lowercase, ensuring a clean, one-line history without commit trailers.
Commit trailers like `Co-Authored-By` are prohibited in conventional commits. The formatting guardrails enforce single-line messages under 72 characters without trailers to reduce ambiguity in the project history.
You use the `skill` scope in a conventional commit message when making changes to skill files. The convention mandates domain-based scopes for all other changes, maintaining strict organization across feature work and refactors.
Limitations of strict conventional commit formatting include mandatory lowercase text, a 72-character limit, and no trailing periods. You cannot use commit trailers and must select from a fixed set of allowed types like feat, fix, or refactor.
vndkubiGenerate conventional commit messages from staged changes.
mikkeymooGenerate a Keep a Changelog changelog from conventional Git commits.
code0100funEnforce conventional commit formatting for git messages across software projects.
metratonEnforce conventional commit format with allowed types and formatting rules.