Generate conventional git commit messages from staged changes.
npx skills add https://github.com/cgeorgii/dots --skill commit-cgeorgii
Please help me install this Agent Skill. Skill: commit Source: https://github.com/cgeorgii/dots/tree/main/coco/dotfiles/claude/skills/commit Command: npx skills add https://github.com/cgeorgii/dots --skill commit-cgeorgii
Conventional commits standardize messaging to improve history readability, automated changelogs, and collaboration by enforcing a consistent structure and clear prefixes.
Ask me to create a conventional commit for your current staged changes.
High-intent search queries and answers about installing and using this skill.
To create conventional commits, you stage your changes and the Skill generates a standardized message using prefixes like feat, fix, docs, or chore to ensure consistent project history.
Supported conventional commit prefixes include feat, fix, refactor, docs, chore, style, and test, allowing you to categorize git messaging for improved history readability and automated changelogs.
You format a git commit message using a heredoc to preserve formatting, applying a concise summary prefix and an optional detailed body to maintain readability across your project history.
Conventional commits standardize messaging to improve history readability, enable automated changelogs, and streamline code review by enforcing a consistent structure with clear prefixes.
Yes, you need to stage changes before generating a conventional commit, and the Skill guides you on how to stage changes and apply the commit via a heredoc script.
foutoucourGenerate conventional commit messages from staged git changes.
plurigridGenerate user-facing changelogs from git commit history.
phel-langCreate git commits following conventional commit message standards.
unfazed-devGenerate semantic Git commit messages and run pre-commit quality gates.
