---
title: "PR Reviewer recipe for Slack and Telegram | Agent Barn"
canonical: "https://agentbarn.dev/recipes/pr-reviewer/platform"
updatedDate: "2026-08-29T16:41:32.000Z"
author: Agent Barn
description: "Reviews pull requests for correctness, clarity, and style, then prepares suggestions for human review. Set it up on Slack or Telegram with Agent Barn."
tags: [Engineering review, AI agents, workflow automation]
categories: [Recipes]
---

# PR Reviewer recipe for Slack and Telegram

A code-review assistant that gives developers an earlier signal on a pull request while preserving a human reviewer’s ownership.

## Choose a platform

### Slack

**Shared with reviewers.** Reports review findings into a channel, so the author and other reviewers see the same notes and can discuss them.

Choose when review is a team activity and findings should be visible to more than the author.

### Telegram

**One developer.** Sends findings to a single chat, giving one developer a private pass over their own pull requests.

Choose when the reviews are for one person and nobody else needs the output.

## Recipe overview

- Category: Engineering review
- Tools: GitHub or Bitbucket + Slack
- Trigger: A pull request is opened or updated in a connected repository.

## Workflow

1. **Inspect change:** Read the pull request, diff, and configured repository context.
2. **Assess quality:** Look for correctness, clarity, and style concerns.
3. **Prepare feedback:** Draft suggestions with references to the relevant change.
4. **Hand off:** Share review notes for a human reviewer to assess.

## Initial setup

1. **Template:** The team’s review criteria, conventions, and instructions.
2. **Skills:** GitHub or Bitbucket access scoped to the intended repositories.
3. **Channels:** A Slack destination for review updates and questions.

## Integrations

### GitHub or Bitbucket

Read pull-request metadata and diffs, then publish review suggestions when allowed.

- Requirement: choose-one
- Credential: A GitHub App or Bitbucket access token restricted to reviewed repositories.

#### Permissions

- Repository metadata: read
- Pull requests and diffs: read
- Review comments: write
- Merge and administration: no access

#### Setup

1. Choose the provider and repositories in scope.
2. Install read permissions first, then add review-comment access if needed.
3. Trigger on opened, reopened, or updated pull requests, not merge or administration events.

## Human review

Treat comments as review suggestions, not approval to merge or deploy code without the team’s established controls.