Agent skill

Git Commit Message

Generate single-line Conventional Commits messages by analyzing git diffs and repository history.

MITAuto-check: notesDevelopment

Install Git Commit Message

skills CLI

$ npx skills add godot-fun/gai --skill git-commit-message -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install godot-fun/gai git-commit-message --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/godot-fun/gai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/git-commit-message .claude/skills/git-commit-message && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "git-commit-message" agent skill from https://github.com/godot-fun/gai/tree/main/.agents/skills/git-commit-message into .claude/skills/git-commit-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit-message", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/godot-fun/gai/tree/main/.agents/skills/git-commit-message

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add godot-fun/gai --skill git-commit-message -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install godot-fun/gai git-commit-message --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/godot-fun/gai.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/git-commit-message .agents/skills/git-commit-message && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "git-commit-message" agent skill from https://github.com/godot-fun/gai/tree/main/.agents/skills/git-commit-message into .agents/skills/git-commit-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit-message", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add godot-fun/gai --skill git-commit-message -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install godot-fun/gai git-commit-message --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/godot-fun/gai.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/git-commit-message .cursor/skills/git-commit-message && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "git-commit-message" agent skill from https://github.com/godot-fun/gai/tree/main/.agents/skills/git-commit-message into .cursor/skills/git-commit-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit-message", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/godot-fun/gai.git --path .agents/skills/git-commit-message

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add godot-fun/gai --skill git-commit-message -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install godot-fun/gai git-commit-message --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/godot-fun/gai.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/git-commit-message .gemini/skills/git-commit-message && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "git-commit-message" agent skill from https://github.com/godot-fun/gai/tree/main/.agents/skills/git-commit-message into .gemini/skills/git-commit-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit-message", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install godot-fun/gai git-commit-message

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add godot-fun/gai --skill git-commit-message -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/godot-fun/gai.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/git-commit-message .github/skills/git-commit-message && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "git-commit-message" agent skill from https://github.com/godot-fun/gai/tree/main/.agents/skills/git-commit-message into .github/skills/git-commit-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit-message", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add godot-fun/gai --skill git-commit-message -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install godot-fun/gai git-commit-message --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/godot-fun/gai.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/git-commit-message .opencode/skills/git-commit-message && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "git-commit-message" agent skill from https://github.com/godot-fun/gai/tree/main/.agents/skills/git-commit-message into .opencode/skills/git-commit-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-commit-message", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: git-commit-message
GitHub stars: 182
Token cost: ~830 tokens
SKILL.md length: 348 words
Files: 2
Skills in repo: 36
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Generate single-line Conventional Commits messages by analyzing git diffs and repository history.

Works in 4 steps: Inspect changes: git status, git diff… → Read recent style: git log --oneline -15 → Draft a single-line Conventional Commits… → …
The user asks for commit messages
SKILL.md covers Rules, Quick Start, Message Format and Workflow, plus 4 more sections
Calls git

What it does

Git Commit Message is an agent skill from godot-fun/gai. Generate single-line Conventional Commits messages by analyzing git diffs and repository history. Use when the user asks for commit messages or help writing commits.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `examples.md`).

It sits in Development, covering Commit messages. It works with Git. The repository describes itself as: A lightweight AI agent and skill workflow framework built with Godot. The licence is MIT.

When your agent uses it

The user asks for commit messages
Help writing commits

Example prompts

“/git-commit-message”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Inspect changes: git status, git diff HEAD (all local changes vs last commit)
Read recent style: git log --oneline -15
Draft a single-line Conventional Commits message matching repo conventions
Return the message only — do not commit unless explicitly asked

What it can do on your machine

Read from SKILL.md and the folder at commit aa1ac71. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Git Commit Message loads about 830 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 348 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~46
When it runs · the whole SKILL.md, loaded when a task matches: ~830

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:87

- Never include secrets (.env, credentials, tokens) in the commit

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from godot-fun/gai at commit aa1ac71, republished under its MIT licence (© godot-fun). 348 words, ~830 tokens.

Download SKILL.mdSave it as .claude/skills/git-commit-message/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: git-commit-message
description: Generate single-line Conventional Commits messages by analyzing git diffs and repository history. Use when the user asks for commit messages or help writing commits.

Git Commit Message

Rules

When inspecting changes for commit messages or change summaries:

Only git diff HEAD defines what changed (all local changes vs last commit)
Never run git diff --staged, git diff --cached, or git diff HEAD --cached
Never infer changes from git status "Changes to be committed"
Never warn about or analyze index vs working-tree mismatches from the staged list
If git diff HEAD is empty, there is nothing to commit — stop

Quick Start

When the user needs a commit message:

Inspect changes: git status, git diff HEAD (all local changes vs last commit)
Read recent style: git log --oneline -15
Draft a single-line Conventional Commits message matching repo conventions
Return the message only — do not commit unless explicitly asked

Run status, diff, and log in parallel when possible.

Message Format

Single line only — no body:

<type>[<scope>]: <subject>

Part	Rules
type	Required. One of: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `perf`, `ci`, `build`, `style`, `revert`
scope	Optional. Module or area in square brackets (e.g. `[auth]`, `[api]`, `[ui]`). Omit brackets entirely if unclear
subject	Imperative mood, lowercase, no trailing period, ≤72 chars. Must stand alone — pack intent into this line

Never add a blank line or body paragraph after the subject.

Type Selection

Type	When
`feat`	New user-facing capability
`fix`	Bug fix
`refactor`	Code change without behavior change
`docs`	Documentation only
`test`	Tests only
`chore`	Maintenance, deps, tooling
`perf`	Performance improvement
`ci`	CI/CD config
`build`	Build system or external deps
`style`	Formatting, whitespace (no logic change)
`revert`	Revert a prior commit

Scope Guidelines

Use existing scopes from recent commits when present
Prefer short, stable names: auth, db, config, deps
Drop scope rather than guess incorrectly

Workflow

Task Progress:
- [ ] Run git status + `git diff HEAD`
- [ ] Read recent git log for style alignment
- [ ] Identify primary change type and scope
- [ ] Draft single-line subject (imperative, self-contained)
- [ ] Check for secrets or files that should not be committed
- [ ] Present message to user

Split vs Single Commit

One logical change → one commit
Unrelated changes (feat + fix in different areas) → suggest splitting
Large refactor + feature → suggest separate commits

Safety

Never include secrets (.env, credentials, tokens) in the commit
Warn if changed files look sensitive
Do not run git commit unless the user explicitly requests it

Output

Present exactly one line in a copy-paste block:

feat[auth]: add jwt token refresh endpoint

fix[ui]: prevent double submit on checkout form

CLI

Copy-paste commands: cli/git-commit-message.md

Additional Resources

More examples: examples.md

Files

SKILL.md and 1 other file in .agents/skills/git-commit-message of godot-fun/gai.

SKILL.md
examples.md

Open the folder on GitHubat commit aa1ac71

Compare with similar skills

Git Commit Message next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Git Commit Message compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Git Commit Message this skillgodot-fun/gai	182	—	~830	Automated safety check: Notes	MIT	today
React Router Release Notes Prepremix-run/react-router	57k	—	~1.1k	Automated safety check: Pass	MIT	today
ToolJet Multi-Repo CommitToolJet/ToolJet	41k	—	~1.3k	Automated safety check: Pass	AGPL-3.0	today
Git Workflow and Versioningaddyosmani/agent-skills	103k	2 repos	~3.5k	Automated safety check: Notes	MIT	5 days ago
React Router Pull Request Creatorremix-run/react-router	57k	—	~2.5k	Automated safety check: Pass	MIT	today
Verdaccio Pull Request Workflowverdaccio/verdaccio	18k	—	~1.9k	Automated safety check: Pass	MIT	today

Similar skills

React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
57k GitHub stars~1.1k tokensUpdated today
DevelopmentAuto-check passed
ToolJet Multi-Repo Commit
ToolJet/ToolJet
Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.
41k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
103k GitHub starsUsed in 2 repos~3.5k tokens
DevelopmentAuto-check: notes
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
57k GitHub stars~2.5k tokensUpdated today
DevelopmentAuto-check passed
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
18k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check passed
Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
23k GitHub stars~575 tokensUpdated today
DevelopmentAuto-check passed

Questions about Git Commit Message

What does Git Commit Message do?

Generate single-line Conventional Commits messages by analyzing git diffs and repository history. Git Commit Message is an agent skill from godot-fun/gai. Generate single-line Conventional Commits messages by analyzing git diffs and repository history.

When should I use Git Commit Message?

Git Commit Message fits situations like: the user asks for commit messages; help writing commits.

How do I install Git Commit Message in Claude Code?

Run `npx skills add godot-fun/gai --skill git-commit-message -a claude-code`. Or copy the skill folder (.agents/skills/git-commit-message in godot-fun/gai) into .claude/skills/git-commit-message in your project. Claude Code loads it when a task matches its description.

How do I install Git Commit Message in Codex?

Run `npx skills add godot-fun/gai --skill git-commit-message -a codex`. Or copy the skill folder (.agents/skills/git-commit-message in godot-fun/gai) into .agents/skills/git-commit-message in your project. Codex loads it when a task matches its description.

Can I use Git Commit Message in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add godot-fun/gai --skill git-commit-message -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-commit-message, .gemini/skills/git-commit-message, .github/skills/git-commit-message and .opencode/skills/git-commit-message in your project.

What does Git Commit Message need to run?

Going by SKILL.md and its folder, Git Commit Message needs the command-line tools its instructions call (git).

Does Git Commit Message access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Git Commit Message safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Git Commit Message use?

Git Commit Message is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Commit Message use?

About 830 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Git Commit Message?

Skills that share tags, products or a category with Git Commit Message: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Commit Message?

godot-fun (a GitHub organization) maintains it in godot-fun/gai, which has 182 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 9, 2026.

Source: godot-fun/gai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Git Commit Message

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Git Commit Message

Rules

Quick Start

Message Format

Type Selection

Scope Guidelines

Workflow

Split vs Single Commit

Safety

Output

CLI

Additional Resources

Files

Compare with similar skills

Similar skills

More from godot-fun/gai

Related

Questions about Git Commit Message