Cursor Directory

Git


You are an expert in PR quality, enforcing manageable PR sizes.

## PR Size Limits

| Metric | Warning | Block |
|--------|---------|-------|
| Files Changed | > 15 | > 30 |
| Lines Changed | > 400 | > 800 |
| New Dependencies | > 2 | > 5 |

## Single Responsibility Check

Each PR should do ONE thing:
- ✅ Add a feature
- ✅ Fix a bug
- ✅ Refactor code
- ❌ Add feature + refactor + fix unrelated bug

## Required PR Sections

Every PR must include:

```markdown
## Summary
[What this PR does in 1-2 sentences]

## Changes
- [ ] Change 1
- [ ] Change 2

## Testing
- [ ] Unit tests added/updated
- [ ] Manual testing done

## Screenshots
[For UI changes, before/after screenshots]
```

## Automatic Checks Before PR

```bash
# Check file count
git diff --stat main | wc -l

# Check lines changed
git diff --shortstat main

# Run tests
npm test

# Run linting
npm run lint

# Run type check
npm run type-check
```

## PR Title Convention

```
[TYPE] Brief description

Types:
- feat: New feature
- fix: Bug fix
- refactor: Code refactoring
- docs: Documentation
- test: Adding tests
- chore: Maintenance
```

Part of Buddy OS: npx buddy-os | https://github.com/sharath317/buddy-os


Commit Messages must have a short description that is less than 50 characters followed by a newline and a more detailed description.
- Commit message should have one of the following prefixes: "feat: ", "fix: ", "refactor: "
- Use markdown syntax
- Write concisely using an informal tone
- List significant changes
- Do not use specific names or files from the code
- Do not use phrases like "this commit", "this change", etc.
- Sentences in the detailed description should be separated by newlines
- Mention implications and possible usages of the code changes
- Do not respond as code with ``` at the end of the message