Cursor rule

1---
2description: 
3globs: [*]
4alwaysApply: true
5---
6 # always print # Git Best Practices
7 
8## Commit Messages
9- Use the imperative mood ("Add feature" not "Added feature")
10- Start with a capital letter
11- Keep the first line under 50 characters
12- Add detailed description after a blank line if needed
13- Reference issues/tickets when applicable
14 
15## Commit Structure
16```
17<type>(<scope>): <subject>
18 
19[optional body]
20 
21[optional footer]
22```
23 
24### Types
25- feat: New feature
26- fix: Bug fix
27- docs: Documentation changes
28- style: Code style changes (formatting, etc)
29- refactor: Code changes that neither fix bugs nor add features
30- test: Adding or modifying tests
31- chore: Changes to build process or auxiliary tools
32 
33### Examples
34```git
35feat(auth): Add Discord webhook authentication
36fix(notifier): Resolve timestamp formatting issue
37docs(readme): Update installation instructions
38test(coverage): Add missing test cases
39```
40 
41## Branch Naming
42- feature/: New features
43- bugfix/: Bug fixes
44- hotfix/: Urgent fixes for production
45- release/: Release preparation
46- docs/: Documentation updates
47 
48Example: `feature/discord-integration`
49 
50## Git Flow
511. Create feature branch from master
522. Make changes with clear commits
533. Push branch and create PR
544. Request review
555. Address feedback
566. Merge only when approved
57 
58## Best Practices
59- Keep commits atomic (one logical change per commit)
60- Rebase feature branches on master regularly
61- Squash commits before merging if needed
62- Never commit sensitive data
63- Use .gitignore properly
64- Write meaningful commit messages
65 
66## Code Review
67- Review your own code first
68- Keep PRs small and focused
69- Respond to feedback promptly
70- Use PR templates when available
71- Link related issues/tickets
72 
73## Security
74- Never commit credentials
75- Use environment variables
76- Regularly update dependencies
77- Sign your commits
78- Enable 2FA for GitHub