Enforce Git commit message types and structured formats for consistent history.
npx skills add https://github.com/Unson-LLC/brainbase --skill git-commit-rules
Please help me install this Agent Skill. Skill: git-commit-rules Source: https://github.com/Unson-LLC/brainbase/tree/main/.claude/skills/git-commit-rules Command: npx skills add https://github.com/Unson-LLC/brainbase --skill git-commit-rules
Brainbase Git commit rules standardize messages to improve readability and traceability of project history.
High-intent search queries and answers about installing and using this skill.
To standardize git commit messages, apply a predefined type list like feat, fix, docs, refactor, chore, and style, followed by a structured summary and optional context sections to explain the change.
The conventional commit format for a feature or bug fix uses a structured type prefix, such as feat or fix, followed by a colon and a concise summary, with optional sections to detail the why and what of the change.
Enforce consistent git commit rules in a CI pipeline by validating messages against a defined type list and structured format, ensuring history readability and traceability across automated builds and pull request reviews.
Yes, you can include additional context in a structured git commit message by appending optional Why and What sections after the initial type and summary, helping reviewers understand the reasoning behind the code changes.
For documentation or refactoring, use the docs or refactor commit types respectively, applying them within a structured message format to categorize changes and maintain a readable project history.
thoreinsteinAnalyze git diffs to plan atomic commits with grouped files and messages.
matteocervelliGenerate CHANGELOG entries from commits using conventional commits and semantic versioning.
Benja-PaulsEnforce Git branch naming, commit message, and pull request conventions.
FaysilAlshareefGenerate changelogs from git commits using Conventional Commits and Keep a Changelog formats.
