git-workflow

A set of rules for using Git, a tool that records code changes, and for writing consistent commit and pull-request messages. It defines commit types, branch names, review steps, and limits on risky practices such as force-pushing shared branches.

In plain words
What is it for?
Use it when creating commits, branches, and pull requests for features, bug fixes, tests, documentation, maintenance, or dependency updates.
Why use it?
It makes project history easier to understand and helps teams review, track, and merge changes consistently.

Cursor rule

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/dasomel/oh-my-cursor/git-workflow
Clone the repo
git clone --depth 1 https://github.com/dasomel/oh-my-cursor
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 348 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.00348
Opus 5 $0.00000 $0.00174
Sonnet 5 $0.00000 $0.00070
Haiku 4.5 $0.00000 $0.00035

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

Security

Grade A, and why

git-workflow 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.

rules/practices/git-workflow.mdc · 59 lines

What it actually says

Git Workflow Standards

Commit Messages (Conventional Commits)

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

Types:

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation only
  • refactor: Code change without feature/fix
  • test: Adding/fixing tests
  • chore: Build, config, dependencies
  • perf: Performance improvement

Examples:

feat(auth): add OAuth2 Google login
fix(api): handle null response from user service
test(parser): add edge cases for empty input
chore(deps): upgrade typescript to 5.7

Rules:

  • Lowercase, no period at end
  • Max 72 chars in first line
  • Imperative mood: "add" not "added"
  • Reference issues: fix(auth): handle session expiry (#142)

Branch Strategy

main          ← production-ready
develop       ← integration branch
feat/name     ← new features
fix/issue-123 ← bug fixes
chore/name    ← maintenance

Pull Request Rules

  • One PR per feature/fix
  • Link to issue: Closes #123
  • Self-review before requesting review
  • All tests passing before review request
  • No force-push to shared branches

Anti-Patterns

  • git commit -m "fix stuff" — meaningless messages
  • Giant PRs (>500 lines changed)
  • Committing generated files
  • Force-pushing to main/develop
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 · 59 lines · 0 tokens per session scan A 1d9a5a1ebbe6

Subscribe to this mod's changes

git-workflow is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 348 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.