What is automatic-git-commit.rules?

Rules for automatically committing staged Git changes, with commit messages following Conventional Commits, a common format such as “feat: add login screen.” They define when changes are logically ready to commit and how to record metadata.

Use them to decide when to commit finished features, tests, refactors, or larger change groups, then create a structured commit from the changed files.

They reduce the chance of leaving completed work uncommitted or using inconsistent commit messages.

automatic-git-commit.rules — Cursor rule by drumnation

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/drumnation/unsplash-smart-mcp-server/automatic-git-commit.rules

Clone the repo

git clone --depth 1 https://github.com/drumnation/unsplash-smart-mcp-server

Made for: Cursor.

Per session 516 This file is loaded in full into every session.

When invoked 516 The same file — it is already loaded in full.

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.00516	$0.00516
Opus 5	$0.00258	$0.00258
Sonnet 5	$0.00103	$0.00103
Haiku 4.5	$0.00052	$0.00052

Measured 2d ago against content hash 9d819e8a00e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

automatic-git-commit.rules 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 2d 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.

.cursor/rules/automatic-git-commit.rules.mdc · 67 lines

What it actually says

Rule: Automatic Git Commit Rules

Purpose: Automatically commit staged changes at logical points in development using conventional commits and metadata logging.

Trigger Conditions:

A feature, function, test, or refactor is logically complete
Total changed lines exceed 300 (across all files)
More than 8 files are staged
A stable group of files is complete (e.g. component + styles + test)
A previously failing test now passes due to these changes
A .rules, README.md, or config file has been modified

Commit Message Structure:

commitSubject (max 50 chars, required): One-line summary using Conventional Commit format (e.g., feat: add login screen)
commitBody (optional): Wrap lines to ~72 chars, summarize key changes, bullet major additions if needed.
commitFooter (optional): For breaking changes or issue refs (e.g., BREAKING CHANGE: or Closes #123)

Commit Process:

Analyze git diff or fallback to git status + file list
Generate structured commit message: Subject, Body, Footer
Stage all changes explicitly: git add -- ${changedFilesList.join(' ')}

Commit using:

echo "${fullMessage}" | git commit -F -

Metadata Logging:

After successful commit, retrieve the hash:
```
git rev-parse HEAD
```

Create a metadata JSON file at .brain/git/commits/[xx]/[hash].json with:

{
  "hash": "<commit hash>",
  "messageSubject": "<subject>",
  "messageBody": "<body>",
  "messageFooter": "<footer>",
  "files": [<file list>],
  "timestamp": "<UTC timestamp>",
  "branch": "<branch name>"
}

Create parent directories with mkdir -p as needed.

Commit Policy Notes:

Skip automatic commit if:
- Files contain WIP, TODO, or FIXME comments
- Code is not in a logically complete state
Prefer small, atomic commits
Avoid committing unrelated changes together

Final Output:

Return only:

{
  "commitHash": "<commit hash>",
  "metadataPath": "<path to metadata file>"
}

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.

2d ago First seen · 67 lines · 516 tokens per session scan A 9d819e8a00e6

Subscribe to this mod's changes

automatic-git-commit.rules is a cursor rule published in the GitHub repository drumnation/unsplash-smart-mcp-server (63 stars, last pushed 7mo ago), licensed MIT. It adds 516 tokens to every session, about $0.0026 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 Testing

automatic-git-commit.rules

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Rule: Automatic Git Commit Rules

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