git

A set of Git rules covering commit messages, branch names, and branch responsibilities. Git is the version-control system used to track code changes and collaborate safely.

In plain words
What is it for?
Use it to name branches, format commits such as `docs: update README`, keep main branches stable, split related changes into smaller commits, and avoid automatic commits.
Why use it?
It gives the team a consistent history and reduces accidental work on stable branches or oversized commits.

Cursor rule for Cursor

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/wangtingyeye/llm-agent-study/git
Clone the repo
git clone --depth 1 https://github.com/WangTingYeYe/llm-agent-study

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 303 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00303
Opus 5 $0.00000 $0.00151
Sonnet 5 $0.00000 $0.00061
Haiku 4.5 $0.00000 $0.00030

Measured yesterday against content hash 83c1a93d7c95, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git 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/backup/python/git.mdc · 33 lines

What it actually says

Git 规范

提交规范

git 提交记录样例:[type]: [description]。一个具体的例子, docs: 更新 README 文件。 以下是 type 的枚举值:

  • feat: 新增功能
  • fix: 修复 bug
  • docs: 文档注释
  • style: 代码格式(不影响代码运行的变动)
  • refactor: 重构、优化(既不增加新功能, 也不是修复bug)
  • perf: 性能优化
  • test: 增加测试
  • chore: 构建过程或辅助工具的变动
  • revert: 回退
  • build: 打包

分支管理

  • main/master: 主分支,保持稳定可发布状态
  • develop: 开发分支,包含最新开发特性
  • feature/*: 功能分支,用于开发新功能
  • bugfix/*: 修复分支,用于修复bug
  • release/*: 发布分支,用于准备发布

重要原则

  • 重要:不要自动提交 git 代码,除非有明确的提示
  • 提交前确保代码通过所有测试
  • 保持提交信息简洁明了,描述清楚变更内容
  • 避免大型提交,尽量将变更分解为小的、相关的提交
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.

  1. yesterday First seen · 33 lines · 0 tokens per session scan A 83c1a93d7c95

Subscribe to this mod's changes

git is a cursor rule published in the GitHub repository WangTingYeYe/llm-agent-study (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 303 tokens. 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-31.