Pull Request Template and Review Guide Generator

You are an engineering manager who establishes code review standards. Create PR templates and review guidelines for this team.

Team size: [NUMBER]
Project type: [WEB / API / LIBRARY / INFRASTRUCTURE]
Release process: [CI/CD / MANUAL / SCHEDULED]
Review requirements: [1 APPROVAL / 2 APPROVALS / CODEOWNERS]
Common issues: [WHAT USUALLY GOES WRONG]

Provide:

**Pull Request Template**
```markdown
## Summary
<!-- Brief description of changes -->

## Type of Change
- [ ] Bug fix (non-breaking change fixing an issue)
- [ ] New feature (non-breaking change adding functionality)
- [ ] Breaking change (fix or feature causing existing functionality to change)
- [ ] Documentation update
- [ ] Refactoring (no functional changes)
- [ ] Performance improvement
- [ ] Test addition/update

## Related Issues
<!-- Link to issues: Closes #123 -->

## Changes Made
<!-- Detailed list of changes -->
- 
- 

## Testing Done
<!-- How did you test these changes? -->
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing performed
- [ ] Tested in staging environment

## Screenshots/Videos
<!-- If UI changes, add screenshots -->

## Checklist
- [ ] My code follows the project's style guidelines
- [ ] I have performed a self-review
- [ ] I have commented my code where necessary
- [ ] I have updated the documentation
- [ ] My changes generate no new warnings
- [ ] New and existing tests pass
- [ ] Any dependent changes have been merged

## Deployment Notes
<!-- Any special deployment considerations -->

## Rollback Plan
<!-- How to rollback if something goes wrong -->
```

**Review Guidelines**

**For Authors:**
1. Keep PRs small (<400 lines ideal)
2. Write descriptive commit messages
3. Self-review before requesting review
4. Respond to feedback within 24 hours
5. Don't merge without required approvals

**For Reviewers:**
1. Review within 24 hours
2. Be constructive and specific
3. Distinguish blocking vs. suggestions
4. Test locally for significant changes
5. Approve explicitly

**Review Checklist**
- [ ] Code correctness
- [ ] Test coverage
- [ ] Security implications
- [ ] Performance impact
- [ ] Documentation
- [ ] Error handling
- [ ] Edge cases

**Comment Prefixes**
- `[BLOCKING]` - Must be fixed
- `[SUGGESTION]` - Optional improvement
- `[QUESTION]` - Need clarification
- `[NITPICK]` - Minor style issue
- `[PRAISE]` - Something done well

**CODEOWNERS File**
```
# Default owners
* @team-lead

# Frontend
/src/components/ @frontend-team

# Backend
/api/ @backend-team
```

You are an engineering manager who establishes code review standards. Create PR templates and review guidelines for this team.

Team size: [NUMBER]
Project type: [WEB / API / LIBRARY / INFRASTRUCTURE]
Release process: [CI/CD / MANUAL / SCHEDULED]
Review requirements: [1 APPROVAL / 2 APPROVALS / CODEOWNERS]
Common issues: [WHAT USUALLY GOES WRONG]

Provide:

**Pull Request Template**
```markdown
## Summary
<!-- Brief description of changes -->

## Type of Change
- [ ] Bug fix (non-breaking change fixing an issue)
- [ ] New feature (non-breaking change adding functionality)
- [ ] Breaking change (fix or feature causing existing functionality to change)
- [ ] Documentation update
- [ ] Refactoring (no functional changes)
- [ ] Performance improvement
- [ ] Test addition/update

## Related Issues
<!-- Link to issues: Closes #123 -->

## Changes Made
<!-- Detailed list of changes -->
- 
- 

## Testing Done
<!-- How did you test these changes? -->
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing performed
- [ ] Tested in staging environment

## Screenshots/Videos
<!-- If UI changes, add screenshots -->

## Checklist
- [ ] My code follows the project's style guidelines
- [ ] I have performed a self-review
- [ ] I have commented my code where necessary
- [ ] I have updated the documentation
- [ ] My changes generate no new warnings
- [ ] New and existing tests pass
- [ ] Any dependent changes have been merged

## Deployment Notes
<!-- Any special deployment considerations -->

## Rollback Plan
<!-- How to rollback if something goes wrong -->
```

**Review Guidelines**

**For Authors:**
1. Keep PRs small (<400 lines ideal)
2. Write descriptive commit messages
3. Self-review before requesting review
4. Respond to feedback within 24 hours
5. Don't merge without required approvals

**For Reviewers:**
1. Review within 24 hours
2. Be constructive and specific
3. Distinguish blocking vs. suggestions
4. Test locally for significant changes
5. Approve explicitly

**Review Checklist**
- [ ] Code correctness
- [ ] Test coverage
- [ ] Security implications
- [ ] Performance impact
- [ ] Documentation
- [ ] Error handling
- [ ] Edge cases

**Comment Prefixes**
- `[BLOCKING]` - Must be fixed
- `[SUGGESTION]` - Optional improvement
- `[QUESTION]` - Need clarification
- `[NITPICK]` - Minor style issue
- `[PRAISE]` - Something done well

**CODEOWNERS File**
```
# Default owners
* @team-lead

# Frontend
/src/components/ @frontend-team

# Backend
/api/ @backend-team
```