Cursor rule

1---
2description: 
3globs: 
4alwaysApply: true
5---
6# Commit Messages and Pull Request Titles
7 
8When creating commits or pull requests in this repository, you MUST follow the conventional commit format defined in `.github/release.yml`.
9 
10## Format
11 
12The general format is: `type(scope): description`
13 
14- `type` is required and must be one of the accepted types
15- `scope` is optional and goes in parentheses
16- `:` colon and space after type/scope
17- `description` starts with lowercase
18 
19## Accepted Types
20 
21Check `.github/labeler.yml` for the current list, which includes:
22- `feat`: New features
23- `fix`: Bug fixes
24- `chore`: Maintenance tasks
25- `docs`: Documentation changes
26- `style`: Code style changes (formatting, etc.)
27- `refactor`: Code refactoring
28- `perf`: Performance improvements
29- `test`: Test additions or modifications
30- `build`: Build system changes
31- `ci`: CI/CD configuration changes
32- `revert`: Reverting previous commits
33 
34## Special Cases
35 
36### Dependencies
37Use specific scope for dependency updates:
38- `chore(deps): update dependencies`
39- `fix(deps): fix vulnerable dependency`
40- `build(deps): update build dependencies`
41 
42### Breaking Changes
43Mark breaking changes by:
441. Adding `!` after the type/scope: `feat!: change API`
452. Or including `BREAKING CHANGE:` in the commit body
46 
47## Examples
48 
49✅ Good:
50- `feat: add user authentication`
51- `fix(api): resolve timeout issue`
52- `chore(deps): update react to v18`
53- `feat!: redesign API endpoints`
54- `docs: update README with new examples`
55 
56❌ Bad:
57- `Feature: Add user auth` (wrong format)
58- `added new feature` (missing type)
59- `Fix API` (missing colon and description)
60 
61## PR Title = First Commit Message
62 
63The PR title should match the format of the main commit message. The labeler will automatically apply labels based on the PR title format.
64 
65**Important**: Any PR that doesn't match these patterns will be labeled as "chore" by default.