Format and validate commit messages according to the Conventional Commits specification.
npx skills add https://github.com/poteto/noodle --skill commit-poteto
Please help me install this Agent Skill. Skill: commit Source: https://github.com/poteto/noodle/tree/main/.agents/skills/commit Command: npx skills add https://github.com/poteto/noodle --skill commit-poteto
Create conventional commit messages that follow the Conventional Commits specification, improving readability and automation of Git history.
Format your next commit as a conventional commit by specifying a type, an optional scope, and a concise subject.
High-intent search queries and answers about installing and using this skill.
Format conventional commit messages by specifying a required type, an optional scope, and a concise subject. This structure enforces header composition rules according to the Conventional Commits specification to improve Git history readability.
A conventional commit is a standardized message format adopting a type, optional scope, and subject. You need it in software development workflows to standardize Git history and automate changelogs and release notes across repositories.
Validate commit message length and structure by applying header composition rules that enforce subject length limits and required type prefixes. This validation provides examples to guide contributors toward correct conventional commit formatting.
You can use an optional scope in your conventional commit header by placing it in parentheses immediately after the type. This scoped structure helps categorize changes within specific modules or components across repositories.
Enforce a commit style guide by validating messages against the Conventional Commits specification, which checks header composition, supports types and optional scopes, and enforces subject length to ensure standardized contributions.
Conventional commit validation fails on subject length when your message exceeds the enforced concise subject limit. The validation process strictly applies header composition rules to ensure your commit subject remains within the specified length boundaries.
mgoodman60Generate descriptive Git commit messages from repository changes with conventional formatting.
FaysilAlshareefGenerate changelogs from git commits using Conventional Commits and Keep a Changelog formats.
avvaleValidate commit messages against the Conventional Commits specification.
rlesniakGenerate conventional commit messages using structured XML templates.
