Generates a conventional git commit message from staged and unstaged changes.
npx skills add https://github.com/northguild/gmt --skill commit-message-northguild
Please help me install this Agent Skill. Skill: commit-message Source: https://github.com/northguild/gmt/tree/main/.agents/skills/commit-message Command: npx skills add https://github.com/northguild/gmt --skill commit-message-northguild
git diff HEAD, git diff --cached, and git status --short to understand the nature of each change before writing anything. - Style matching: Studies git log --oneline -10 to replicate your repo's subject-line conventions, including type prefixes, scopes, casing, and length limits. - Safe, read-only operation: Never runs git commit, git add, git push, or any state-modifying command; it outputs a copyable message only. - Use Case: After finishing a bug fix across several files, ask for a commit message and receive a conventional-commit subject like fix(dox): stop clipping the globe plus an optional explanatory body, ready to paste into your terminal. ## Quick Start Ask the assistant to write a commit message for the changes currently in your working tree.High-intent search queries and answers about installing and using this skill.
Ask the assistant to write a commit message and it will run git diff HEAD, git diff --cached, and git status --short to understand your changes. It then drafts a conventional-commit subject and optional body as a copyable code block.
Use the format type(scope): description, such as feat(domination): calendar boundaries and zone-aware buckets. The Skill checks git log --oneline -10 to match your repo's exact casing, verb tense, and prefix conventions before drafting.
No, it only runs read-only git commands like diff, status, and log. It never executes git commit, git add, git push, or any command that modifies git state; it outputs the message text for you to use yourself.
The Skill produces one message per output and flags when changes clearly belong in separate commits. It suggests splitting the commit rather than inventing a misleading combined subject.
The message is designed to be pasted into a shell command wrapped in double quotes, so any embedded double quote would break the command. Backticks are used instead for code and names.
Soyio-idCreate logically scoped git commits with Conventional Commit messages from working-tree changes.
eriknovakCreate a conventional commit, push the branch, and open a GitHub pull request.
vh2224Review code changes for security, performance, bug, and test coverage issues.
harekiSplit pending worktree changes into ordered atomic commits matching repository conventions.