Copilot PR Review Skill

Description

## Copilot PR Review Skill

### Overview
Leverage Copilot for thorough pull request reviews that catch bugs, security issues, and maintainability concerns before merging.

### Automatic PR Summary
When Copilot generates a PR summary, it should include:
- **What changed:** High-level summary of modifications
- **Why:** The motivation or issue being addressed
- **How:** Brief technical approach description
- **Impact:** What parts of the system are affected
- **Testing:** What was tested and how

### Review with Copilot Chat
Use these prompts in the PR review context:

**Overall Review:**
```
@github Review this pull request. Focus on:
1. Logic errors and edge cases
2. Security vulnerabilities
3. Performance implications
4. Code style consistency
5. Test coverage gaps
```

**Specific File Review:**
```
@github Review the changes in src/services/auth.ts.
Check for: token handling security, error handling completeness,
and backward compatibility with existing clients.
```

**Test Adequacy:**
```
@github Are the tests in this PR sufficient?
Identify missing test cases for edge cases, error paths,
and boundary conditions in the changed code.
```

### Line-Level Review Comments
Use Copilot suggestions on specific lines:
- Hover over changed lines and ask Copilot for suggestions
- Request explanations for complex changes: "Explain this change"
- Ask for alternatives: "Is there a simpler way to do this?"
- Flag potential issues: "Could this cause a race condition?"

### Review Checklist Template
Add this to your PR template for Copilot-assisted reviews:

```markdown
## Review Checklist
- [ ] Code compiles and passes all existing tests
- [ ] New tests cover the changes adequately
- [ ] No hardcoded secrets or credentials
- [ ] Error handling is comprehensive
- [ ] Database queries are optimized (no N+1)
- [ ] API changes are backward compatible
- [ ] UI changes are responsive and accessible
- [ ] Documentation is updated if needed
```

### Batch Review Workflow
1. Start with the PR summary to understand scope
2. Review the most critical files first (auth, data access, API)
3. Use Copilot to explain unfamiliar code patterns
4. Check test files match the implementation changes
5. Verify configuration changes are safe for all environments

### Responding to Review Feedback
- Use Copilot to generate fix suggestions for review comments
- Ask Copilot to refactor code addressing multiple review comments at once
- Generate commit messages that reference the review feedback

Free to copy and use. Compatible with GitHub Copilot, GPT-5.

How to Use This Skill

Tags

Compatible Agents

Version History

Install Command

Related Prompts