What is git-commit-format?

A set of rules for writing commit messages in the Conventional Commits format, such as `fix: correct login error`, with required sign-off details.

Use it when generating or creating commits, including feature changes, bug fixes, documentation updates, tests, and breaking changes.

It keeps commit history consistent and makes the type and purpose of each change easier to understand.

git-commit-format — Skill for Claude Code by openshift-eng/ai-helpers

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add openshift-eng/ai-helpers --skill git-commit-format

Clone the repo

git clone --depth 1 https://github.com/openshift-eng/ai-helpers

Made for: Claude Code.

Or install git, the plugin that ships this one along with the rest of its 2 skills, 10 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/git-commit-format/github.svg)](https://agentmods.dev/skills/openshift-eng/ai-helpers/git-commit-format)

Your own site

<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/git-commit-format"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/git-commit-format/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/git-commit-format"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/git-commit-format.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 888 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00020	$0.00888
Opus 5.5	$0.00008	$0.00355
Sonnet 5.5	$0.00004	$0.00178
Haiku 4.5	$0.00002	$0.00089

Measured 1mo ago against content hash 26efbfbb9f67, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-commit-format scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/git/skills/git-commit-format/SKILL.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Name

openshift-developer:git-commit-format

Synopsis

/openshift-developer:git-commit-format

Description

Applies conventional commit formatting rules when generating commit messages. This skill is loaded as context for other skills and workflows — it defines the commit message format, required footers, and validation rules.

Implementation

Commit Message Format

<type>(<scope>): <description>

[optional body]

[footers]

Commit Types

feat: New features
fix: Bug fixes
docs: Documentation changes
style: Code style changes (formatting, etc.)
refactor: Code refactoring (no functional changes)
test: Adding/updating tests
chore: Maintenance tasks
build: Build system or dependency changes
ci: CI/CD changes
perf: Performance improvements
revert: Revert previous commit

Breaking Changes

With ! to draw attention:

feat!: send email when product shipped

With BREAKING CHANGE footer:

feat: allow config to extend other configs

BREAKING CHANGE: `extends` key now used for extending config files

Required Footers

Signed-off-by

ALWAYS include Signed-off-by footer with name and email.

Get credentials in this priority order:

Environment variables: $GIT_AUTHOR_NAME and $GIT_AUTHOR_EMAIL
Git config: git config user.name and git config user.email
If neither configured, ask user to provide details

Commit-Message-Assisted-by

ALWAYS include when Claude assists with creating or generating the commit message:

Commit-Message-Assisted-by: Claude (via Claude Code)

Gitlint Validation Rules

Run make run-gitlint to validate commit messages (if the repo has a gitlint target)
Title line: 120 characters maximum
Body line: 140 characters maximum per line
Use conventional commit format
Include required footers (Signed-off-by)
No trailing whitespace

Return Value

Commit message: A conventional commit message with type, scope, description, body, and all required footers

Read the full file on GitHub · 138 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 138 lines · 20 tokens per session scan A 26efbfbb9f67

Subscribe to this mod's changes

git-commit-format is a skill published in the GitHub repository openshift-eng/ai-helpers (121 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 888 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Commits Git and workflow

create-pr

Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.

prisma/orm · 48 tokens

git-commit

Generate well-formatted git commit messages following conventional commit standards.

ThinkInAIXYZ/deepchat · 15 tokens

repo-sync

Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.

davidondrej/skills · 25 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

contributing

How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…

HugoRCD/evlog · 68 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens