Enforce conventional commit message types, scope, and descriptions in Git workflows.
npx skills add https://github.com/otahontas/nix --skill git-commit-otahontas
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/otahontas/nix/tree/main/home/configs/pi-coding-agent/skills/git-commit Command: npx skills add https://github.com/otahontas/nix --skill git-commit-otahontas
This Skill helps teams adopt a standardized git commit message format, improving changelog generation, code review clarity, and project history readability.
Use the git-commit skill to craft a conventional commit message for a new feature, e.g., feat(auth): add remember-me support.
High-intent search queries and answers about installing and using this skill.
Conventional git commit messages standardize version-control history by enforcing specific types, scopes, and descriptions. This format improves changelog generation, code review clarity, and project readability across collaborative repositories.
To format a git commit message for a feature, use the conventional commit type 'feat' followed by an optional scope and description, such as 'feat(auth): add remember-me support' to convey clear intent and impact.
For fixes and documentation, use the 'fix' and 'docs' conventional commit types. Supported types also include feat, style, refactor, perf, test, build, ci, chore, and revert to standardize various workflow scenarios.
Yes, enforcing conventional commits works for collaborative repositories by guiding scope and description constraints. This ensures automation-friendly changelogs and easier review workflows across multiple contributors.
The best way to structure a git commit message for maintenance tasks is using the 'chore' type with a clear scope and description, ensuring the commit adheres to conventional guidelines for project history readability.
heikopanjasStage all working tree changes and create a conventional commit.
sgcarstrendsGenerate CHANGELOG.md from conventional commits using semantic-release.
89jobrienAutomate pre-commit quality gates and conventional commit workflows for Git projects.
dgalarzaGuide Git commit messages to follow the Conventional Commits structure.
