write-pr-description

# Write PR Description

Create structured pull request descriptions that provide context for reviewers.

## Structure

```markdown
## Summary
[1-2 sentence overview]

## What Changed
- [Bullet point 1]
- [Bullet point 2]
- [Bullet point 3]

## Why
[Explanation of why this change was needed]

## Testing
### Automated
- [x] Unit tests pass
- [x] Integration tests pass
- [x] Linting passes

### Manual
- [x] [Specific manual test performed]
- [x] [Another manual verification]

## Screenshots
[If UI changes]
![Description](url)

## Related Issues
Closes #123
Refs #456
```

## Sections

### Summary
- 1-2 sentences explaining the PR at a high level
- What is being added/fixed/changed
- Why it matters

### What Changed
- Bullet list of specific changes
- Focus on "what" not "how"
- Group related changes together

### Why
- Business context or technical motivation
- Problem being solved
- Why this approach was chosen

### Testing
Split into Automated and Manual:

**Automated**:
- Commands that were run
- All tests that pass
- CI/CD checks

**Manual**:
- Specific manual testing performed
- Edge cases verified
- Performance testing

### Screenshots (if applicable)
- Before/after comparisons for UI changes
- Error states
- Different screen sizes/browsers

### Related Issues
- Link to tickets: `Closes #123`
- Link to related PRs: `Refs #456`
- Link to documentation

## Example

```markdown
## Summary
Adds JWT token refresh mechanism to prevent unexpected session expiration. Tokens are automatically refreshed 5 minutes before expiry.

## What Changed
- Added token refresh endpoint `/api/auth/refresh`
- Implemented automatic refresh timer in auth middleware
- Added token expiry checking logic
- Updated auth context to handle refresh flow
- Added tests for refresh scenarios

## Why
Users were experiencing unexpected logouts when their sessions expired during active use. This caused data loss and poor UX. Automatic token refresh keeps sessions alive as long as users are active.

##