---
name: Pull Request Description
description: Template for writing clear and informative PR descriptions
tokens: 280
---

# Pull Request Description Template

When creating a PR description, use this structure for clarity:

## Summary
Brief 1-2 sentence summary of what this PR does and why.

## Changes Made
- List the key changes, grouped logically
- Use bullet points for clarity
- Include file/component names when helpful

## Testing
Describe how you tested the changes:
- [ ] Unit tests added/updated
- [ ] Manual testing performed
- [ ] Integration tests pass
- [ ] Edge cases verified

## Screenshots (if applicable)
Include screenshots for UI changes:
- Before/after comparisons
- Different states (loading, error, success)
- Mobile/responsive views

## Checklist
- [ ] Code follows project style guidelines
- [ ] Self-review completed
- [ ] Documentation updated
- [ ] No breaking changes (or migration path documented)
- [ ] Reviewer(s) assigned

## Related Issues
Fixes #[issue-number]
Related to #[issue-number]

## Notes for Reviewers
Any context that would help reviewers understand the changes or areas that need particular attention.
