Validate Git commit messages against the Conventional Commits 1.0.0 specification.
npx skills add https://github.com/patrickhaahr/dotfiles --skill commits
Please help me install this Agent Skill. Skill: commits Source: https://github.com/patrickhaahr/dotfiles/tree/main/opencode/.config/opencode/skills/commits Command: npx skills add https://github.com/patrickhaahr/dotfiles --skill commits
This skill helps teams avoid ambiguous or inconsistent commit messages by ensuring every commit follows the Conventional Commits 1.0.0 specification, improving readability and automation.
Use this skill to draft a conventional commit message for the current changes after verifying diffs and history.
High-intent search queries and answers about installing and using this skill.
To enforce conventional commit messages, a validation skill checks Git commit type prefixes like feat, fix, and docs against the Conventional Commits 1.0.0 specification. It validates type, scope, and description formatting to reduce ambiguity in project history.
The correct conventional commit format requires a type prefix, an optional scope in parentheses, and a descriptive summary. This skill validates these elements against the Conventional Commits 1.0.0 specification and suggests the properly formatted message for your review.
To generate a conventional commit message, review your Git diffs and history for consistency, then use this skill to draft a message. It applies the Conventional Commits 1.0.0 specification to propose a correctly formatted commit summary.
Yes, this conventional commit validator supports standard types including feat, fix, docs, style, refactor, test, and chore. It enforces these type prefixes per the Conventional Commits 1.0.0 specification to improve readability and automation.
Your team should use conventional commits to avoid ambiguous or inconsistent project history. Standardized commit messages following the Conventional Commits 1.0.0 specification improve readability and enable automation for release management.
stacklokGenerates commit messages from staged files for common use cases.
allanninalConvert git commits into changelogs following Keep a Changelog and Conventional Commits.
GaryOcean428Enforce conventional commits, branch naming, Gitflow, and PR hygiene.
avvaleValidate commit messages against the Conventional Commits specification.
