Table of contents
- Install GitHub Skill
- Create Review Prompts
- Set Up Automation Rules
- Configure Notifications
- Example Workflows
- Next Steps
- FAQ
Install GitHub Skill
openclaw skills install github
Authorize with repo and admin:repo_hook scopes for full PR access.
Create Review Prompts
Create ~/.openclaw/workspace/prompts/pr-review.md:
# PR Review Prompt
Analyze this pull request:
- Check for breaking changes
- Verify tests pass
- Suggest code improvements
- Check for security issues
- Verify documentation updates
Provide a concise review with specific, actionable feedback.
Set Up Automation Rules
Create ~/.openclaw/workspace/prompts/pr-auto-review.md:
# Auto PR Review Rules
Auto-review PRs that meet:
- From trusted team members
- Less than 500 lines changed
- No breaking changes
- All tests passing
Skip manual review for these criteria.
Flag others for manual review.
Configure Notifications
Add to ~/.openclaw/openclaw.json:
{
"automation": {
"pr-monitor": {
"schedule": "*/5 * * * *",
"prompt": "file:prompts/pr-auto-review.md",
"target": "slack"
},
"pr-alerts": {
"schedule": "*/1 * * * *",
"prompt": "file:prompts/pr-review.md",
"target": ["slack", "telegram"]
}
}
}
Example Workflows
Auto-Approve Documentation PRs
If PR only changes docs and tests pass:
- Add approval label
- Auto-merge after 1 hour if no objections
Security Scan on New PRs
Run security analysis on all new PRs:
- Check for exposed secrets
- Scan dependencies for vulnerabilities
- Flag any sensitive data changes
Next Steps
FAQ
Q: Can OpenClaw merge PRs automatically?
A: Yes, but enable approvals for safety. Use auto-merge rules carefully.
Q: How does it handle large PRs?
A: It can summarize and focus on key changes. Configure size limits if needed.
Q: Can it review code quality?
A: Yes. Configure linting and test coverage checks.
Q: What about GitLab MRs?
A: Use gitlab skill for merge requests instead of PRs.