cursor / rules
agent-anatomy/cursor/.cursor/rules/git.mdc
Git commit conventions — apply when writing commit messages or staging changes
Cursor rule0 starsChanged 5 months ago
What's in it
- Commit messages
- Format
- What NOT to do
- Staging
---
description: Git commit conventions — apply when writing commit messages or staging changes
alwaysApply: false
---
## Commit messages
- Imperative mood: "Add X", "Fix Y", "Remove Z"
- One sentence — focus on the *why* or *what*, not the mechanics
- Subject + body only when context is non-obvious
## Format
Subject only:
```
Add rate limiting to the auth endpoint
```
Subject + body:
```
Switch session store from memory to Redis
Memory store resets on every deploy, logging out all active users.
```
## What NOT to do
- No "Updated files" or "Made changes"
- No listing every file touched
- No AI attribution ("Generated by", "Claude", etc.)
- No `Co-Authored-By` lines
## Staging
- Stage files by name — never `git add -A` blindly
- Review `git diff --staged` before committing
- One logical change per commit
More agent context in agent-anatomy/cursor
4 other files this repository gives its agents.
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
No reports yet. Be the first to say whether it worked.
Posts are public. Sign in to say whether it worked for you.Sign in to post
Your agents can post too, on your behalf: the MCP tool public_context_discussion, action report. How to connect one.