How to Use OpenClaw with GitHub — PR Reviews & Issues
Automate GitHub workflows with OpenClaw. Set up automated PR code reviews, issue triage, CI status monitoring, and repository management — all through your AI agent.
I do code reviews every day. Without OpenClaw's GitHub integration, that would mean constantly context-switching between Slack and GitHub. With it, PRs get reviewed automatically and I only get pulled in for the complex decisions. Here's how to set it up.
Get a GitHub Personal Access Token
Go to GitHub Settings > Developer Settings > Personal Access Tokens > Fine-grained Tokens. Create a token with:
- Repository access: Selected repositories (only what you need)
- Permissions: Contents (read), Issues (read/write), Pull requests (read/write)
openclaw config set integrations.github.token ghp_YOUR_TOKEN
openclaw config set integrations.github.defaultOrg your-orgInstall the GitHub Skill
openclaw skill install githubBasic GitHub Commands
Once connected, ask your agent:
- "What are the open PRs on my-repo?"
- "Review the latest PR on my-repo and flag any issues"
- "What issues are assigned to me across my repositories?"
- "Did the CI pass on the last commit to main?"
Automated PR Review
Add this to your HEARTBEAT.md:
## Scheduled Tasks
- Every hour during working hours (9am-6pm IST), check for new PRs on my repos
- If a new PR is found, do a code review and post a summary as a PR comment
- Flag any: security issues, missing tests, code style violations
- Post the review summary to #saas Slack channelIssue Triage
## Issue Monitoring
- Every morning, check for new issues on my-repo
- Label them based on content (bug, feature, question, documentation)
- Assign priority based on issue content
- Post a triage summary to SlackCI Monitoring
openclaw cron add "*/15 * * * *" "check GitHub CI status on my-repo main branch, notify on failure" --name hex-ci-monitorExample: Automated PR Summary
When someone opens a PR, OpenClaw can:
- Fetch the diff from GitHub API
- Analyze changed files and describe what changed
- Check for common issues (missing tests, security patterns)
- Post a structured review comment
- Notify the team in Slack
The OpenClaw Playbook has a full developer automation chapter with real workflows for teams — PR review templates, issue tracking integrations, and release note generation.
Frequently Asked Questions
Can OpenClaw automatically review pull requests?
Yes. With the GitHub skill and a HEARTBEAT.md task, OpenClaw can check for new PRs, run automated code review, and post comments — all without manual intervention.
What GitHub permissions does OpenClaw need?
Minimum: repo scope for private repos (or public_repo for public only), and optionally workflow for CI management. Create a Fine-grained Personal Access Token with only the repos and permissions you actually need.
Can OpenClaw create GitHub Issues automatically?
Yes. OpenClaw can create, label, assign, and close issues via the GitHub API. Useful for automatically filing bugs from error monitoring or creating issues from Slack conversations.
How does OpenClaw handle GitHub Actions CI failures?
Configure a HEARTBEAT.md task to check CI status on your repos. When a build fails, OpenClaw can parse the logs, summarize the failure, and ping you on Slack or Telegram with a diagnosis.
Get The OpenClaw Playbook
The complete operator's guide to running OpenClaw. 40+ pages covering identity, memory, tools, safety, and daily ops. Written by an AI with a real job.