What is git-commit-format?

Rules for writing Git commit messages in Conventional Commits format, a shared pattern such as `fix(scope): description`.

Use them when creating commits, including the required change type, optional scope and body, and project-specific attribution lines.

They make commit history consistent and identify the kind of change each commit contains.

git-commit-format — Cursor rule by openshift

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.

agentmods

npx agentmods add rules/openshift/hypershift/git-commit-format

Clone the repo

git clone --depth 1 https://github.com/openshift/hypershift

Made for: Cursor.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 0 findings. Scan, not verified.

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	$0.00011	$0.00671
Opus 5	$0.00005	$0.00336
Sonnet 5	$0.00002	$0.00134
Haiku 4.5	$0.00001	$0.00067

Measured yesterday against content hash f14aaecfc5d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

.cursor/rules/git-commit-format.mdc · 108 lines

How it starts

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

Commit Message Formatting Rules

When to apply: When generating commit messages or discussing commit practices

Commit Message Format

Use conventional commits format:

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

[optional body]

Signed-off-by: <name> <email>
Assisted-by: <model-name> (via Cursor)

Signed-off-by

When you include: Signed-off-by: <name> <email>
Get name and email using this priority order:
1. Environment variables: $GIT_AUTHOR_NAME and $GIT_AUTHOR_EMAIL
2. Git config: git config user.name and git config user.email
3. If neither configured, ask user to provide details

Commit Types

feat: New features
fix: Bug fixes
docs: Documentation changes
style: Code style changes
refactor: Code refactoring
test: Adding/updating tests
chore: Maintenance tasks
build: Build system or dependencies
ci: CI/CD changes
perf: Performance improvements
revert: Revert previous commit

Conventional Commit Specification

This project uses the conventional commit, here is the specification https://www.conventionalcommits.org/en/v1.0.0/#specification.

Conventional Commit Examples

Commit message with description and breaking change footer

feat: allow provided config object to extend other configs

BREAKING CHANGE: `extends` key in config file is now used for extending other config files

Commit message with ! to draw attention to breaking change

feat!: send an email to the customer when a product is shipped

Commit message with scope and ! to draw attention to breaking change

feat(api)!: send an email to the customer when a product is shipped

Commit message with both ! and BREAKING CHANGE footer

chore!: drop support for Node 6

BREAKING CHANGE: use JavaScript features not available in Node 6.

Commit message with no body

docs: correct spelling of CHANGELOG

Commit message with scope

feat(lang): add Polish language

Read the full file on GitHub · 108 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.

yesterday First seen · 108 lines · 11 tokens per session scan A f14aaecfc5d8

Subscribe to this mod's changes

git-commit-format is a cursor rule published in the GitHub repository openshift/hypershift (538 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 671 once invoked, about $0.0001 per session on Opus 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-08-30.

Git and workflow Writing and docs

git-commit-format

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Commit Message Formatting Rules

Commit Message Format

Signed-off-by

Commit Types

Conventional Commit Specification

Conventional Commit Examples

What this file has done since we first saw it

Other cursor rules, from other repositories

angular-20

dev-standard

typescript

coolify-ai-docs

python_lib

specs