What is git-conventions?

Git workflow rules based on Conventional Commits, a standard format for writing structured commit messages. They also set language requirements and naming rules for branches, pull requests, reviews, and issues.

Use them when creating commits, branches, pull requests, code-review comments, or issue titles and descriptions.

They keep repository history and collaboration messages consistent, making changes easier to understand, search, and release.

git-conventions — Cursor rule by gifflet

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/gifflet/cursor-like-pro/git-conventions

Clone the repo

git clone --depth 1 https://github.com/gifflet/cursor-like-pro

Made for: Cursor.

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

When invoked 2,561 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.00009	$0.02561
Opus 5	$0.00005	$0.01281
Sonnet 5	$0.00002	$0.00512
Haiku 4.5	$0.00001	$0.00256

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

Security

Grade A, and why

git-conventions 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/git-conventions.mdc · 384 lines

How it starts

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

Git Conventions and Workflow Guidelines 🔄

Language Requirements

All git-related text MUST be written in English:

Commit messages
Branch names
Pull request titles and descriptions
Code review comments
Issue titles and descriptions

Commit Message Format

All commit messages MUST follow the Conventional Commits specification:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Types

feat: A new feature
fix: A bug fix
docs: Documentation only changes
style: Changes that do not affect the meaning of the code (formatting, etc)
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools
ci: Changes to CI configuration files and scripts

Scope

The scope should be the name of the component affected (as perceived by the person reading the changelog).

Examples:

feat(auth): add login with Google
fix(api): handle null response from server
docs(readme): update installation steps

Description

Use the imperative, present tense: "change" not "changed" nor "changes"
Don't capitalize first letter
No dot (.) at the end
Write in english

Branch Naming Convention

Branches should follow this pattern:

<type>/<short-description>

For features and fixes that are tracked in a project management system, include the ticket number:

<type>/<ticket-number>-<short-description>

Examples:

feat/add-google-auth
fix/handle-null-responses
docs/update-readme
feat/PROJ-123-add-google-auth
fix/PROJ-456-handle-null-responses

Workflow Guidelines

Protected Branches
- main (or master): Production-ready code, protected branch
- Direct commits to protected branches are NOT allowed
- All changes must come through Pull Requests

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

2d ago First seen · 384 lines · 9 tokens per session scan A 1abee799e09d

Subscribe to this mod's changes

git-conventions is a cursor rule published in the GitHub repository gifflet/cursor-like-pro (17 stars, last pushed 1y ago), licensed MIT. It adds 9 tokens to every session and 2,561 once invoked, about $0.0000 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.

Code review Git and workflow Writing and docs ai cursor cursor-rules mcp mcp-client tips

git-conventions