Enforce Conventional Commits format for git commits and PR/MR titles.
npx skills add https://github.com/dmythro/agent-skills --skill git-commit-dmythro
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/dmythro/agent-skills/tree/main/skills/git-commit Command: npx skills add https://github.com/dmythro/agent-skills --skill git-commit-dmythro
Conventional commits provide a standardized format for git commits and PR/MR titles, enabling clear history, easier code reviews, and automation tooling compatibility. Not for PR workflows (git-pr), CI/CD status (git-ci), or git branch management.
Format your next commit using a conventional type-prefix and optional scope to align with project conventions.
High-intent search queries and answers about installing and using this skill.
Conventional commits standardize git commit messages by requiring a type prefix, lowercase imperative description, and optional scope. This format ensures machine-parseable history, simplifying changelogs, release notes, and automation tooling compatibility.
To format conventional commits, start your git commit message with a type prefix, add an optional scope, and use a lowercase imperative description. Following these rules ensures a consistent message structure for code reviews and automated release notes.
Yes, enforcing conventional commits applies to both everyday git commits and PR/MR titles. It ensures a consistent message structure across feature work, bug fixes, and documentation updates for individual and team projects.
Use breaking change rules and scopes in conventional commits to clearly communicate major modifications and component boundaries. This practice ensures machine-parseable history and improves review clarity for automated changelogs.
Do not use conventional commits for CI/CD status checks, git branch management, or PR workflows. This standard specifically solves the lack of standardized commit messages for feature work, bug fixes, and documentation updates.
The best way to automate changelog generation is by enforcing conventional commits across your git commit history. Standardizing type prefixes and scopes creates a machine-parseable history that automation tooling can easily process.
ian-pascoeGenerate conventional git commit messages and stage related file changes.
mvandermeulenGenerate project changelogs and release notes from Conventional Commits history.
lanegridEnforce branching strategies, Conventional Commits, and PR workflows in Git.
awinogradovConverts non-conventional commit messages into conventional commit formats.
