agentleFS
Sign inSign up

ai-coding-rules / rules

Luxvil/ai-coding-rules/.cursor/rules/71-git-workflow.mdc

USE WHEN: working with Git operations, commits, branches

Cursor rule3 starsChanged 8 months ago

What's in it

  1. Git Workflow Rules
  2. Commit Messages
  3. Branch Naming
  4. Best Practices
  5. Pull Requests
---
description: "USE WHEN: working with Git operations, commits, branches"
globs: []
alwaysApply: false
priority: 70
---

# Git Workflow Rules

## Commit Messages
- Use conventional commits: `type(scope): message`
- Types: feat, fix, docs, style, refactor, test, chore
- Keep subject line <72 characters
- Add body for complex changes

## Branch Naming
- `feature/` - new features
- `fix/` - bug fixes
- `refactor/` - code improvements
- `docs/` - documentation only

## Best Practices
- Commit early and often (checkpoints)
- Never commit secrets or credentials
- Don't commit generated files
- Keep commits atomic (one logical change)
- Write meaningful commit messages

## Pull Requests
- Reference related issues
- Include testing instructions
- Keep PRs focused and reviewable
- Request reviews from relevant team members

More agent context in Luxvil/ai-coding-rules

24 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.

Reports can't be read right now.

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.