feat: Add comprehensive GitHub PR template

- Create .github/PULL_REQUEST_TEMPLATE.md with structured format
- Include change type checkboxes, testing checklist, and reviewer guidance
- Add sections for breaking changes, related issues, and deployment notes
- Follow GitHub best practices for PR templates
- Improve contribution quality and review process

This template helps contributors provide consistent, comprehensive
information for pull requests and streamlines the review process.

Author: andrewmarconi

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,96 @@
+## Description
+
+Brief description of the changes made in this PR.
+
+## Type of Change
+
+<!-- What type of change does this PR introduce? -->
+<!-- Please check the one that applies to this PR using "x". -->
+
+- [ ] 🐛 **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** (updates to documentation)
+- [ ] 🎨 **Style** (code style changes, formatting, etc.)
+- [ ] ♻️ **Refactor** (code refactoring, no functional changes)
+- [ ] ⚡ **Performance** (performance improvements)
+- [ ] ✅ **Test** (adding or updating tests)
+- [ ] 🔧 **Build/CI** (changes to build process or CI configuration)
+- [ ] 🔒 **Security** (security-related changes)
+- [ ] 🚀 **Release** (version bump, release notes, etc.)
+
+## Changes Made
+
+<!-- List the specific changes made in this PR -->
+
+- Change 1
+- Change 2
+- Change 3
+
+## Testing
+
+<!-- Describe the testing you performed -->
+
+### Testing Completed
+
+- [ ] Unit tests pass (`uv run python -m pytest tests/`)
+- [ ] Integration tests pass
+- [ ] Linting passes (`uv run ruff check flytrap/`)
+- [ ] Type checking passes (`uv run python -m mypy flytrap/ --ignore-missing-imports`)
+- [ ] Manual testing completed
+- [ ] Documentation updated
+
+### Test Coverage
+
+<!-- If applicable, describe test coverage changes -->
+- [ ] New tests added for new functionality
+- [ ] Existing test coverage maintained or improved
+- [ ] Test coverage report attached
+
+## Screenshots (if applicable)
+
+<!-- Add screenshots for UI changes, new features, or before/after comparisons -->
+
+## Breaking Changes
+
+<!-- If this PR introduces breaking changes, describe them here -->
+
+**Breaking Changes:**
+- List any breaking changes here
+- Include migration instructions if needed
+
+## Related Issues
+
+<!-- Link to related issues this PR addresses -->
+
+Closes #<!-- issue number -->
+Related to #<!-- issue number -->
+
+## Additional Notes
+
+<!-- Any additional information, context, or considerations -->
+
+## Checklist
+
+<!-- Please check all that apply -->
+
+- [ ] My code follows the project's style guidelines
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings or errors
+- [ ] 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
+- [ ] Any dependent changes have been merged and published in downstream modules
+
+## Reviewer Notes
+
+<!-- Notes for reviewers, if any -->
+
+## Deployment Notes
+
+<!-- Notes about deployment, if any special considerations are needed -->
+
+---
+
+Thank you for contributing to Flytrap! 🎉