## PR Title Format

**Please ensure your PR title follows one of these formats:**

- `feat: <description>` - New features (triggers MINOR version bump)
- `fix: <description>` - Bug fixes (triggers PATCH version bump)
- `breaking: <description>` or `BREAKING CHANGE: <description>` - Breaking changes (triggers MAJOR version bump)
- `perf: <description>` - Performance improvements (triggers PATCH version bump)
- `refactor: <description>` - Code refactoring (triggers PATCH version bump)
- `docs: <description>` - Documentation only (no version bump)
- `chore: <description>` - Maintenance tasks (no version bump)
- `test: <description>` - Test additions/changes (no version bump)
- `ci: <description>` - CI/CD changes (no version bump)
- `style: <description>` - Code style changes (no version bump)

## Description

Please provide a clear and concise description of what this PR does.

## Changes Made

- [ ] List the specific changes made
- [ ] Include any breaking changes
- [ ] Note any dependencies added/removed

## Testing

- [ ] Unit tests pass
- [ ] Integration tests pass (if applicable)
- [ ] Manual testing completed
- [ ] Documentation updated (if needed)

## Related Issues

Fixes #(issue number)

## Checklist

- [ ] PR title follows the format guidelines above
- [ ] Code follows the project's style guidelines
- [ ] Self-review completed
- [ ] Tests added/updated as needed
- [ ] Documentation updated as needed
- [ ] All tests passing
- [ ] Ready for review

## Additional Notes

Any additional information that reviewers should know.