Name: gh pr review
Author: Cyborgninja21

Prompt file imported from Cyborgninja21/pychivalry (.github/prompts/gh pr review.prompt.md). Copyright stays with the author.

# gh pr review - Review Pull Request Assistant

When the user asks for help reviewing pull requests, follow this structured workflow:

## Reviewing Pull Requests

The `gh pr review` command allows you to approve, request changes, or comment on PRs directly from the command line.

## Basic Usage

### Review Types

```bash
# Approve PR
gh pr review 42 --approve

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

# Comment without approval/rejection
gh pr review 42 --comment

Review with Feedback

1. Approve with Comment

gh pr review 42 --approve --body "LGTM! Great implementation of scope validation.

Code quality is excellent and tests are comprehensive."

2. Request Changes with Details

gh pr review 42 --request-changes --body "Good progress, but needs some fixes:

## Required Changes
- Add type hints to new functions
- Extract magic numbers to constants
- Add docstrings for public methods

## Testing
- Add unit tests for edge cases
- Update integration tests

## Documentation
- Update CHANGELOG.md
- Add usage examples"

3. Comment Only (No Approval/Rejection)

gh pr review 42 --comment --body "A few suggestions:

- Consider using dataclass for scope context
- Performance looks good
- Documentation is clear

Nice work overall!"

Review from File

# Read review feedback from file
gh pr review 42 --approve --body-file review_comments.md

Complete Review Workflows

Thorough Code Review

# 1. Checkout PR for testing
gh pr checkout 42

# 2. Run tests
pytest tests/ -v

# 3. Check code quality
flake8 pychivalry/
mypy pychivalry/

# 4. Review changes
git diff main...HEAD

# 5. Submit review
gh pr review 42 --approve --body "✅ Code Review Complete

## Testing
- All tests pass (142/142)
- Manually tested with sample files
- Performance verified

## Code Quality
- Type hints complete
- Documentation clear
- Follows project conventions

Approved for merge!"

# 6. Return to your branch
git checkout main

Request Changes Workflow

# 1. Review code
gh pr view 42 --diff | less

# 2. Request changes with checklist
gh pr review 42 --request-changes --body "Please address these items:

## Code Quality
- [ ] Add type hints to scope_validator.py
- [ ] Extract SCOPE_TYPES constant
- [ ] Fix indentation in line 234

## Testing
- [ ] Add test for empty scope chain
- [ ] Add test for invalid scope type
- [ ] Update integration test fixtures

## Documentation
- [ ] Add docstring to validate_scope_chain()
- [ ] Update CHANGELOG.md
- [ ] Add example to README

Please update when complete!"

Quick Approval

# Simple approval for straightforward changes
gh pr review 42 --approve --body "LGTM! ✅"

Review Multiple PRs

# Review multiple PRs in batch
for pr in 42 43 44; do
  gh pr view $pr --diff | less
  gh pr review $pr --approve --body "Approved"
done

Review Best Practices Checklist

# Before reviewing, check:

# 1. View PR description
gh pr view 42

# 2. Check CI status
gh pr checks 42

# 3. Review file changes
gh pr view 42 --diff

# 4. Checkout and test locally
gh pr checkout 42
pytest tests/
npm test

# 5. Check code quality
# - Type hints present
# - Documentation complete
# - Tests comprehensive
# - No obvious bugs

# 6. Submit review
gh pr review 42 --approve --body "Thorough review complete. All checks pass."

Review Options Reference

--approve              Approve PR
--request-changes      Request changes before merge
--comment              Comment without approval/rejection
--body TEXT            Review feedback
--body-file FILE       Read feedback from file

Quick Reference

# Approve
gh pr review 42 --approve

# Approve with comment
gh pr review 42 --approve --body "LGTM!"

# Request changes
gh pr review 42 --request-changes --body "Please fix..."

# Comment only
gh pr review 42 --comment --body "Nice work!"

# Review from file
gh pr review 42 --approve --body-file review.md

Troubleshooting

Can't Submit Review

# Check permissions
gh auth status

# Ensure PR exists and is open
gh pr view 42

Review Not Showing

# Refresh PR view
gh pr view 42 --web

# Check if review was submitted
gh pr view 42 --json reviews

Best Practices

Test Locally: Checkout and run tests before reviewing
Be Specific: Provide clear, actionable feedback
Be Constructive: Focus on improvement, not criticism
Check Everything: Code, tests, docs, performance
Use Checklists: Ensure nothing is missed
Approve Quickly: Don't block good PRs unnecessarily
Request Changes Clearly: Use markdown formatting
Follow Up: Check if requested changes are addressed
Praise Good Work: Acknowledge excellent code
Review Timely: Don't leave PRs waiting

```prompt # gh pr review - Review Pull Request Assistant When the user asks for help reviewing pull requests, follow this structured workflow: ## Reviewing Pull Requests The `gh pr review` command allows you to approve, request changes, or comment on PRs directly from the command line. ## Basic Usage ### Review Types ```bash # Approve PR gh pr review 42 --approve # Request changes gh pr review 42 --request-changes # Comment without approval/rejection gh pr review 42 --comment ``` ## Review with Feedback ### 1. **Approve with Comment** ```bash gh pr review 42 --approve --body "LGTM! Great implementation of scope validation. Code quality is excellent and tests are comprehensive." ``` ### 2. **Request Changes with Details** ```bash gh pr review 42 --request-changes --body "Good progress, but needs some fixes: ## Required Changes - Add type hints to new functions - Extract magic numbers to constants - Add docstrings for public methods ## Testing - Add unit tests for edge cases - Update integration tests ## Documentation - Update CHANGELOG.md - Add usage examples" ``` ### 3. **Comment Only (No Approval/Rejection)** ```bash gh pr review 42 --comment --body "A few suggestions: - Consider using dataclass for scope context - Performance looks good - Documentation is clear Nice work overall!" ``` ## Review from File ```bash # Read review feedback from file gh pr review 42 --approve --body-file review_comments.md ``` ## Complete Review Workflows ### Thorough Code Review ```bash # 1. Checkout PR for testing gh pr checkout 42 # 2. Run tests pytest tests/ -v # 3. Check code quality flake8 pychivalry/ mypy pychivalry/ # 4. Review changes git diff main...HEAD # 5. Submit review gh pr review 42 --approve --body "✅ Code Review Complete ## Testing - All tests pass (142/142) - Manually tested with sample files - Performance verified ## Code Quality - Type hints complete - Documentation clear - Follows project conventions Approved for merge!" # 6. Return to your branch git checkout main ``` ### Request Changes Workflow ```bash # 1. Review code gh pr view 42 --diff | less # 2. Request changes with checklist gh pr review 42 --request-changes --body "Please address these items: ## Code Quality - [ ] Add type hints to scope_validator.py - [ ] Extract SCOPE_TYPES constant - [ ] Fix indentation in line 234 ## Testing - [ ] Add test for empty scope chain - [ ] Add test for invalid scope type - [ ] Update integration test fixtures ## Documentation - [ ] Add docstring to validate_scope_chain() - [ ] Update CHANGELOG.md - [ ] Add example to README Please update when complete!" ``` ### Quick Approval ```bash # Simple approval for straightforward changes gh pr review 42 --approve --body "LGTM! ✅" ``` ## Review Multiple PRs ```bash # Review multiple PRs in batch for pr in 42 43 44; do gh pr view $pr --diff | less gh pr review $pr --approve --body "Approved" done ``` ## Review Best Practices Checklist ```bash # Before reviewing, check: # 1. View PR description gh pr view 42 # 2. Check CI status gh pr checks 42 # 3. Review file changes gh pr view 42 --diff # 4. Checkout and test locally gh pr checkout 42 pytest tests/ npm test # 5. Check code quality # - Type hints present # - Documentation complete # - Tests comprehensive # - No obvious bugs # 6. Submit review gh pr review 42 --approve --body "Thorough review complete. All checks pass." ``` ## Review Options Reference ```bash --approve Approve PR --request-changes Request changes before merge --comment Comment without approval/rejection --body TEXT Review feedback --body-file FILE Read feedback from file ``` ## Quick Reference ```bash # Approve gh pr review 42 --approve # Approve with comment gh pr review 42 --approve --body "LGTM!" # Request changes gh pr review 42 --request-changes --body "Please fix..." # Comment only gh pr review 42 --comment --body "Nice work!" # Review from file gh pr review 42 --approve --body-file review.md ``` ## Troubleshooting ### Can't Submit Review ```bash # Check permissions gh auth status # Ensure PR exists and is open gh pr view 42 ``` ### Review Not Showing ```bash # Refresh PR view gh pr view 42 --web # Check if review was submitted gh pr view 42 --json reviews ``` ## Best Practices 1. **Test Locally**: Checkout and run tests before reviewing 2. **Be Specific**: Provide clear, actionable feedback 3. **Be Constructive**: Focus on improvement, not criticism 4. **Check Everything**: Code, tests, docs, performance 5. **Use Checklists**: Ensure nothing is missed 6. **Approve Quickly**: Don't block good PRs unnecessarily 7. **Request Changes Clearly**: Use markdown formatting 8. **Follow Up**: Check if requested changes are addressed 9. **Praise Good Work**: Acknowledge excellent code 10. **Review Timely**: Don't leave PRs waiting ```

{ "prompt": "```prompt\n# gh pr review - Review Pull Request Assistant\n\nWhen the user asks for help reviewing pull requests, follow this structured workflow:\n\n## Reviewing Pull Requests\n\nThe `gh pr review` command allows you to approve, request changes, or comment on PRs directly from the command line.\n\n## Basic Usage\n\n### Review Types\n\n```bash\n# Approve PR\ngh pr review 42 --approve\n\n# Request changes\ngh pr review 42 --request-changes\n\n# Comment without approval/rejection\ngh pr review 42 --comment\n```\n\n## Review with Feedback\n\n### 1. **Approve with Comment**\n\n```bash\ngh pr review 42 --approve --body \"LGTM! Great implementation of scope validation.\n\nCode quality is excellent and tests are comprehensive.\"\n```\n\n### 2. **Request Changes with Details**\n\n```bash\ngh pr review 42 --request-changes --body \"Good progress, but needs some fixes:\n\n## Required Changes\n- Add type hints to new functions\n- Extract magic numbers to constants\n- Add docstrings for public methods\n\n## Testing\n- Add unit tests for edge cases\n- Update integration tests\n\n## Documentation\n- Update CHANGELOG.md\n- Add usage examples\"\n```\n\n### 3. **Comment Only (No Approval/Rejection)**\n\n```bash\ngh pr review 42 --comment --body \"A few suggestions:\n\n- Consider using dataclass for scope context\n- Performance looks good\n- Documentation is clear\n\nNice work overall!\"\n```\n\n## Review from File\n\n```bash\n# Read review feedback from file\ngh pr review 42 --approve --body-file review_comments.md\n```\n\n## Complete Review Workflows\n\n### Thorough Code Review\n\n```bash\n# 1. Checkout PR for testing\ngh pr checkout 42\n\n# 2. Run tests\npytest tests/ -v\n\n# 3. Check code quality\nflake8 pychivalry/\nmypy pychivalry/\n\n# 4. Review changes\ngit diff main...HEAD\n\n# 5. Submit review\ngh pr review 42 --approve --body \"✅ Code Review Complete\n\n## Testing\n- All tests pass (142/142)\n- Manually tested with sample files\n- Performance verified\n\n## Code Quality\n- Type hints complete\n- Documentation clear\n- Follows project conventions\n\nApproved for merge!\"\n\n# 6. Return to your branch\ngit checkout main\n```\n\n### Request Changes Workflow\n\n```bash\n# 1. Review code\ngh pr view 42 --diff | less\n\n# 2. Request changes with checklist\ngh pr review 42 --request-changes --body \"Please address these items:\n\n## Code Quality\n- [ ] Add type hints to scope_validator.py\n- [ ] Extract SCOPE_TYPES constant\n- [ ] Fix indentation in line 234\n\n## Testing\n- [ ] Add test for empty scope chain\n- [ ] Add test for invalid scope type\n- [ ] Update integration test fixtures\n\n## Documentation\n- [ ] Add docstring to validate_scope_chain()\n- [ ] Update CHANGELOG.md\n- [ ] Add example to README\n\nPlease update when complete!\"\n```\n\n### Quick Approval\n\n```bash\n# Simple approval for straightforward changes\ngh pr review 42 --approve --body \"LGTM! ✅\"\n```\n\n## Review Multiple PRs\n\n```bash\n# Review multiple PRs in batch\nfor pr in 42 43 44; do\n gh pr view $pr --diff | less\n gh pr review $pr --approve --body \"Approved\"\ndone\n```\n\n## Review Best Practices Checklist\n\n```bash\n# Before reviewing, check:\n\n# 1. View PR description\ngh pr view 42\n\n# 2. Check CI status\ngh pr checks 42\n\n# 3. Review file changes\ngh pr view 42 --diff\n\n# 4. Checkout and test locally\ngh pr checkout 42\npytest tests/\nnpm test\n\n# 5. Check code quality\n# - Type hints present\n# - Documentation complete\n# - Tests comprehensive\n# - No obvious bugs\n\n# 6. Submit review\ngh pr review 42 --approve --body \"Thorough review complete. All checks pass.\"\n```\n\n## Review Options Reference\n\n```bash\n--approve Approve PR\n--request-changes Request changes before merge\n--comment Comment without approval/rejection\n--body TEXT Review feedback\n--body-file FILE Read feedback from file\n```\n\n## Quick Reference\n\n```bash\n# Approve\ngh pr review 42 --approve\n\n# Approve with comment\ngh pr review 42 --approve --body \"LGTM!\"\n\n# Request changes\ngh pr review 42 --request-changes --body \"Please fix...\"\n\n# Comment only\ngh pr review 42 --comment --body \"Nice work!\"\n\n# Review from file\ngh pr review 42 --approve --body-file review.md\n```\n\n## Troubleshooting\n\n### Can't Submit Review\n\n```bash\n# Check permissions\ngh auth status\n\n# Ensure PR exists and is open\ngh pr view 42\n```\n\n### Review Not Showing\n\n```bash\n# Refresh PR view\ngh pr view 42 --web\n\n# Check if review was submitted\ngh pr view 42 --json reviews\n```\n\n## Best Practices\n\n1. **Test Locally**: Checkout and run tests before reviewing\n2. **Be Specific**: Provide clear, actionable feedback\n3. **Be Constructive**: Focus on improvement, not criticism\n4. **Check Everything**: Code, tests, docs, performance\n5. **Use Checklists**: Ensure nothing is missed\n6. **Approve Quickly**: Don't block good PRs unnecessarily\n7. **Request Changes Clearly**: Use markdown formatting\n8. **Follow Up**: Check if requested changes are addressed\n9. **Praise Good Work**: Acknowledge excellent code\n10. **Review Timely**: Don't leave PRs waiting\n\n```", "variables": [], "notes": "When the user asks for help reviewing pull requests, follow this structured workflow:", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/Cyborgninja21/pychivalry", "path": ".github/prompts/gh pr review.prompt.md", "ref": "91a5c896ef6225e4cfc023e76b93770ca1868085", "url": "https://github.com/Cyborgninja21/pychivalry/blob/91a5c896ef6225e4cfc023e76b93770ca1868085/.github/prompts/gh pr review.prompt.md", "key": "Cyborgninja21/pychivalry/.github/prompts/gh pr review.prompt.md" } } }

gh pr review

About