Enforce conventional commit format with allowed types and formatting rules.
npx skills add https://github.com/metraton/gaia --skill git-conventions-metraton
Please help me install this Agent Skill. Skill: git-conventions Source: https://github.com/metraton/gaia/tree/main/skills/git-conventions Command: npx skills add https://github.com/metraton/gaia --skill git-conventions-metraton
Ensures consistent, readable Git history by standardizing commit messages and PR preparation, reducing review friction and improving traceability.
Follow the commit format rules to craft your next commit message.
High-intent search queries and answers about installing and using this skill.
To format git commit messages, use the conventional structure type(scope): short description. Specify the type, scope, subject, body, and footers to ensure a clear, readable project history and reduce review friction.
Allowed commit types in a conventional git workflow include feat, fix, refactor, docs, test, chore, ci, perf, style, and build. Using these standard types categorizes changes to improve traceability and reduce review friction.
Git commit subject line rules require a lowercase first character, imperative mood, a maximum of 72 characters, and no trailing period. Following these formatting rules ensures concise, readable commit titles for easier history navigation.
Write the git commit body and footers by separating them from the subject with a blank line. Use the body for detailed context and footers for metadata, ensuring structured, traceable documentation for features and fixes.
You need conventional commit formatting when standardizing git history for features and fixes. It enforces consistent messages and PR preparation, reducing review friction and improving traceability across the project.
mgoodman60Generate descriptive Git commit messages from repository changes with conventional formatting.
bychrisrManage GitHub repository operations with CI/CD configuration and automated quality gates.
jgezelscorpEnforce branch naming, commit conventions, and manage GitHub issues and pull requests.
nmdraParse Git commit history and format CHANGELOG.md entries per Keep a Changelog standards.
