PR Review → Telegram Feedback

OpenCode finishes a change, opens a PR, then OpenClaw reviews the diff and replies in Telegram with suggestions and a clear merge verdict including critical fixes to apply first.

This showcase demonstrates a fully automated code review pipeline where OpenCode (or any coding agent) completes a change, pushes a branch, and opens a pull request on GitHub. OpenClaw then picks up the PR event — either via a GitHub webhook skill or a cron-based polling check — reads the diff, and performs a structured code review. The results land directly in your Telegram chat with actionable suggestions, severity labels, and a clear merge/hold verdict. What makes this setup powerful is the feedback loop it creates. Instead of switching between your IDE, GitHub's PR interface, and a chat window, you get the review summary exactly where you're already paying attention — Telegram. The agent highlights critical fixes that must be applied before merging, flags optional improvements, and even suggests refactoring opportunities. For solo developers or small teams, this replaces the waiting game of async PR reviews with near-instant feedback. The workflow is surprisingly straightforward to replicate. You need OpenClaw with Telegram configured, a GitHub webhook or polling skill that watches for new PRs, and a prompt template that structures the review output. The agent uses its exec and web_fetch tools to pull the diff, then applies code review heuristics before formatting the response for Telegram's markdown.

Tags: review, github, telegram, code-review

Category: devtools

Tips

  • Set up a GitHub webhook skill to trigger reviews automatically on PR creation — don't rely on manual prompts
  • Include a structured prompt template that categorizes findings by severity (critical, warning, suggestion) for scannable output
  • Use Telegram's topic threads to separate PR reviews from general chat — keeps your main conversation clean
  • Add a 'merge confidence score' to the review template so you can quickly glance at whether it's safe to merge
  • Pair with a cron job that checks for stale PRs and sends reminder nudges to Telegram

Community Feedback

OpenCode finishes the change → opens a PR → OpenClaw reviews the diff and replies in Telegram with suggestions and a clear merge verdict. This is the dev workflow I didn't know I needed.

— OpenClaw Showcase

The PR review to Telegram pipeline is genuinely useful for solo devs. No more context-switching to GitHub just to check if something's ready to merge.

— Reddit r/openclaw

Frequently Asked Questions

Does this work with private GitHub repositories?

Yes, as long as OpenClaw has a GitHub personal access token with repo scope configured. The agent uses the token to fetch diffs from private repos just like public ones.

Can I customize what the code review focuses on?

Absolutely. The review quality depends on your prompt template. You can instruct the agent to focus on security issues, performance, style consistency, or any combination. Many users include project-specific coding standards in their AGENTS.md.

How does this handle large PRs with many changed files?

For large diffs, it's best to set a file-count or line-count threshold in your skill. Beyond that threshold, the agent can summarize changes per file rather than reviewing line-by-line, keeping Telegram messages readable.

Can I trigger the review from Telegram instead of automatically?

Yes. You can simply paste a PR URL into your Telegram chat and ask OpenClaw to review it. The automated webhook approach just removes that manual step.