Generate Conventional Commits messages with validated type, scope, subject length, and body wrapping.
npx skills add https://github.com/sontek/agent-skills --skill commit-sontek
Please help me install this Agent Skill. Skill: commit Source: https://github.com/sontek/agent-skills/tree/main/plugins/agent-skills/skills/commit Command: npx skills add https://github.com/sontek/agent-skills --skill commit-sontek
This Skill standardizes commit messages by enforcing conventional commits and best practices, improving git history readability and automation-friendly formatting.
Use this skill to generate a well-formed commit message for a new feature or bug fix.
High-intent search queries and answers about installing and using this skill.
To format git commit messages using conventional commits, you generate a structured message with a type, scope, and subject. This enforces subject length and body wrapping to maintain a clean, machine-readable git history.
The conventional commits specification for a git history is a formatting standard that defines commit types like feat and fix. It uses a structured type, scope, subject, and body to make commit logs machine-readable and automation-friendly.
You generate a conventional commit message for a bug fix by using the fix type template. The skill provides templates for common scenarios like feat and fix, validating subject length and body wrapping to ensure proper formatting.
Yes, enforcing conventional commits supports PR and release workflows. By standardizing commit messages with a well-structured type and scope, it enables reliable changelog generation and aligns commits with automated release processes.
A limitation of standardizing git commits is that it requires strict adherence to type, scope, subject length, and body wrapping validation. Teams must consistently apply these conventional commit templates to avoid breaking automated changelog and release workflows.
TheDecipheristGenerate conventional commit messages from git diffs using the Conventional Commits format.
dhruvinrsoniParse git history to generate changelogs and release notes.
alex-ilgayevCreate conventional Git commits with feature branches and staged changes.
channingwaltonGenerate conventional commit messages from staged git diffs.
