Compose and validate Git commit messages against a fixed type vocabulary and format.
npx skills add https://github.com/kieranpotts/skills --skill commit-kieranpotts
Please help me install this Agent Skill. Skill: commit Source: https://github.com/kieranpotts/skills/tree/main/skills/commit Command: npx skills add https://github.com/kieranpotts/skills --skill commit-kieranpotts
<type>: <description> format from a closed vocabulary, validates existing messages against the same rules, and writes the matching changelog entry. ## Core Features & Use Cases - Message Composition: Reads a changeset via git diff and proposes one or more atomic commit messages using a fixed type vocabulary (behavior, fix, refactor, chore, and more), with optional flags like BREAKING or WIP. - Message Validation: Checks subject lines against a validation regex and a 72-character limit, reporting a pass/fail verdict per message with the exact rule violated. - Changelog Updates: Adds a matching entry to the project's unreleased changelog section when the commit lands on a trunk or short-lived branch, skipping chore: commits. - Use Case: After staging a bug fix, ask the agent to write the commit message; it reads the diff, picks fix as the type, proposes fix: handle empty repository in git-amend, and updates the changelog — without staging, committing, or pushing anything. ## Quick Start Ask the agent to write a commit message for the current staged changes, or to check whether the messages on this branch pass validation.High-intent search queries and answers about installing and using this skill.
Use the format `<type>: <description>` with a type from a fixed vocabulary such as behavior, fix, refactor, or chore, followed by a lowercase imperative description. The subject must match a validation regex and stay within 72 characters, with optional flags like BREAKING appended after a dash.
Read the branch history with git log and check each subject line against the validation regex and the 72-character limit. The skill reports a pass/fail verdict per message and names the specific rule each failure violates.
Common causes are a type outside the closed vocabulary, a description that is not lowercase imperative, a trailing period, Conventional Commits artifacts like scopes or `!` markers, or a subject line exceeding 72 characters. The skill identifies which rule each failing message violates.
Yes, via a flag suffix in the form `<type>: <description> - BREAKING` rather than the Conventional Commits `!` marker. Other flags include EXPERIMENT, INCOMPAT, TEMPORARY, and WIP, each with defined semantics.
No. The skill only composes and validates messages and updates the changelog where one exists. It never stages, commits, amends, or pushes, so the user keeps final control over what enters history.
SocketDevRelocates a Git version bump commit to the tip of the default branch.
rnavarychGuide Git branching, commit conventions, and pull request workflows.
HyperxqEnforce Conventional Commits and run Git hooks via Lefthook.
fartmonarchStandardize Chinese Git commit messages and changelog configuration.