• Fixes #
• Related to #

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🎨 Style/UI changes
• ♻️ Code refactoring (no functional changes)
• ⚡ Performance improvements
• 🔧 Build/CI changes
• 🧪 Tests

• Local development
• Staging environment
• Production-like environment

• Unit tests pass
• Integration tests pass
• Manual testing completed
• Cross-browser testing (if applicable)
• Mobile testing (if applicable)

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings or errors
• I have run npm run lint and fixed any issues

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have tested the changes in multiple browsers (if applicable)
• I have tested the changes on mobile devices (if applicable)

• I have made corresponding changes to the documentation
• I have updated the README.md if necessary
• I have added/updated JSDoc comments for new functions
• I have updated type definitions if necessary

• I have added translations for new text strings
• I have tested the changes in different languages (if applicable)

• This PR introduces breaking changes
• I have documented the breaking changes in the description
• I have updated the migration guide (if applicable)

// Old code example

// New code example

• Code logic and correctness
• Performance implications
• Security considerations
• User experience
• Accessibility
• Browser compatibility

• Pull and test the branch locally
• Verify the fix/feature works as described
• Check for edge cases
• Verify no regressions in existing functionality

Thank you for contributing to Evolution Manager! 🚀