graph LR
    A[Create PR] --> B[Automated Checks]
    B --> C[Request Review]
    C --> D[Reviewer Review]
    D --> E{Approved?}
    E -->|Yes| F[Merge]
    E -->|No| G[Request Changes]
    G --> H[Author Updates]
    H --> D

# Request specific reviewers
gh pr create --reviewer @username1,@username2

# Request review from team
gh pr create --team-reviewers @team-name

# Request code owner review (CODEOWNERS file)
gh pr create --reviewer codeowners

✅ "Consider extracting this logic to a separate function for reusability"
✅ "This approach might cause performance issues with large datasets. Have you tested with >10K records?"
✅ "Great solution! One suggestion: could we add error handling for edge cases?"

❌ "This is wrong" (without explanation)
❌ "Rewrite this" (without guidance)
❌ Personal attacks or sarcasm
❌ Nitpicking formatting issues (use linters instead)

# .github/workflows/code-review.yml
name: Code Review Automation

on:
  pull_request:
    types: [opened, synchronize, reopened]

jobs:
  automated-review:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3

      - name: Run linter
        run: |
          npm run lint

      - name: Check PR size
        uses: kodiakh/pr-size-action@v1
        with:
          size_threshold: 400

      - name: Request review from CODEOWNERS
        uses: actions/github-script@v6
        with:
          script: |
            const files = await github.rest.pulls.listFiles({
              owner: context.repo.owner,
              repo: context.repo.repo,
              pull_number: context.payload.pull_request.number
            });
            // Request review based on file changes

# .github/CODEOWNERS
# Format: file-pattern @reviewer

# Global owner
* @tech-lead

# Specific directories
/api/ @api-team @backend-lead
/frontend/ @frontend-team @frontend-lead
/docs/ @documentation-team

# File patterns
*.md @documentation-team
*.sql @database-team

## Pre-Review Checklist

- [ ] All automated tests pass
- [ ] Manual testing completed
- [ ] Code follows style guide
- [ ] Self-review performed
- [ ] PR description is clear and complete
- [ ] Related issues are linked
- [ ] Breaking changes are documented
- [ ] Dependencies are updated
- [ ] No console.log or debug code
- [ ] Environment variables are documented

## Review Checklist

### Functionality
- [ ] Code implements requirements correctly
- [ ] Edge cases are handled
- [ ] Error handling is appropriate
- [ ] Performance is acceptable

### Code Quality
- [ ] Code is readable and maintainable
- [ ] Naming conventions are followed
- [ ] DRY principle is followed
- [ ] Functions have single responsibility

### Security
- [ ] No hardcoded credentials
- [ ] Input validation is present
- [ ] SQL injection protection
- [ ] XSS prevention for web apps
- [ ] Authorization checks are correct

### Testing
- [ ] Unit tests cover new code
- [ ] Integration tests are updated
- [ ] Tests are meaningful and readable

## Merge Checklist

- [ ] All reviewers approved
- [ ] All CI checks pass
- [ ] Conversation is resolved
- [ ] No outstanding change requests
- [ ] PR is up to date with main branch
- [ ] Merge commit message is appropriate

# Suggest splitting large PR
gh pr comment "This PR is quite large. Consider splitting into:
1. Core logic changes
2. UI updates
3. Tests and docs"

# Mark PR as urgent
gh pr edit --add-label "urgent,hotfix"
gh pr edit --add-reviewer @oncall

## Breaking Changes

### API Changes
- Endpoint `/api/v1/users` renamed to `/api/v1/accounts`
- Response format changed for `GET /api/v1/orders`

### Migration Guide
```bash
# Update API calls
sed -i 's|/api/v1/users|/api/v1/accounts|g' app.js

---

## Quick Reference

### GitHub CLI Commands

```bash
# Create PR with reviewers
gh pr create --title "Feature: Add user authentication" \
  --body "Implements #123" \
  --reviewer @team-lead \
  --label enhancement

# View PR status
gh pr view 123

# Add reviewer to existing PR
gh pr edit 123 --add-reviewer @username

# Approve PR
gh pr review 123 --approve

# Request changes
gh pr review 123 --request-changes

# Comment on PR
gh pr comment 123 --body "Looks good, just one suggestion..."

# Merge PR
gh pr merge 123 --squash --delete-branch

# List open PRs
gh pr list --state open --limit 20