Draft conventional git commit messages with type-prefixed subjects.
npx skills add https://github.com/shift-editor/shift --skill commit-shift-editor
Please help me install this Agent Skill. Skill: commit Source: https://github.com/shift-editor/shift/tree/main/.claude/skills/commit Command: npx skills add https://github.com/shift-editor/shift --skill commit-shift-editor
It prevents messy git history by enforcing consistent, conventional commit messages that are easy to read and grep later.
<type>: <concise description> so git log --oneline stays readable.Use case: You update the editor and also fix a crash caused by that UI change; you’ll end up with two commits like feat: ... and fix: ..., rather than one vague “misc changes” commit.
Ask the skill to draft commit messages for your proposed changes and to propose a split if multiple logical changes are present.
High-intent search queries and answers about installing and using this skill.
Conventional commit messages follow the `<type>: <concise description>` format to keep git history readable. This skill drafts these messages by enforcing allowed types and formatting rules, reducing ambiguity in your version control workflow.
To split changes into separate git commits, group unrelated modifications into distinct logical units before staging. This skill identifies when multiple logical changes are present and proposes a split, drafting individual messages for each.
A body is needed in a conventional commit message when the concise subject cannot fully explain the why behind the change. This skill prompts you for reasoning and checks whether the type and subject rules require a body.
Allowed types for conventional commits include features, fixes, refactors, and build or CI updates. This skill enforces these specific types in the commit subject to maintain a changelog-like history across code, test, docs, and tooling changes.
Yes, this commit message skill works for documentation and test changes. It applies conventional commit formatting across code, tests, docs, and tooling updates, ensuring the entire repository workflow maintains a readable git log.
AleksaRistic216Create concise git commit messages and commit staged changes.
Jonathan0823Generate git commit messages following the conventional commits format.
exception-coderGenerate standardized commit messages from staged diffs with user confirmation.
voidrotGenerate changelogs and release notes from commit history and tags.