About git-committer
git-committer is a skill that drafts conventional commit messages from a repository’s current changes. It checks staged changes first, otherwise considers unstaged and untracked files, and can suggest splitting large change sets into multiple commits.
Key features
- 01Inspect repository status and diffs
- 02Prioritize staged changes
- 03Include untracked file contents
- 04Use recent commits for context
- 05Suggest split messages for large changes
Use cases
- 01Draft a message for staged changes
- 02Summarize unstaged and untracked work
- 03Separate a large change set into commits
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/git-committerin Claude Code to confirm it loaded.
Details
From the project READMEGenerating a git commit message
Instructions
- Run
git status --short,git diff, andgit diff --stagedto gather current changes, including untracked files - If there are staged files, generate commit message suggestions using only staged changes (including staged newly added files)
- If there are no staged files, include unstaged diff changes and untracked files in the suggestion context
- For untracked files, inspect file names and content (for example with
git status --shortandcat/sed) so they are represented in the suggested message - For more context, get the last 5 to 10 commit messages as well
- Suggest a commit message:
- The commit message should be a single line
- The commit message should be a summary of the changes
- The commit message should follow conventional commit conventions
- If there too many changes, suggest multiple commit messages with a split of files between each commit message
Best practices
- Use present tense
- After the tag (e.g.
feat:), the first letter should be capitalized, unless it's a symbol like a function name
Comments
Markdown supported