← Back to Field Notes
Using AI with GitHub – Code Review, PR Summaries, and Automation
Field Notes #11
Playbook
May 25, 2026
7 min read

Using AI with GitHub – Code Review, PR Summaries, and Automation

Connect your AI assistant to GitHub and get automated PR summaries, code review help, issue triage, and commit analysis – all from your messenger.

What if your AI assistant could summarize a pull request in three sentences, flag security concerns in a diff, or create a GitHub issue directly from a Telegram message? Amplify's GitHub integration connects your repositories to your daily messenger – bringing code awareness into your communication flow instead of requiring you to context-switch to another tool.

What the GitHub Integration Does

Once you connect your GitHub account, your Amplify assistant gains these capabilities:

Summarize pull requests: "Summarize PR #42" → 3-line summary of what changed and why
Review code changes: "Review this PR for security issues" → analysis of the diff with flagged concerns
Create issues: "Create an issue: the login page crashes on mobile Safari" → issue created in your repo with proper formatting
Track repository activity: "What happened in the repo today?" → digest of commits, PRs, and issues
Commit context: "What was the last change to the payments module?" → relevant commit history

All of this works from Telegram, WhatsApp, Discord, or Slack — wherever you message your assistant.

Why This Matters

The typical developer workflow for staying on top of a repository involves:

1.Open GitHub in a browser tab
2.Navigate to the right repo
3.Click through PRs, issues, and commits
4.Mentally parse diffs and discussions
5.Switch back to your messaging or work context

With the GitHub integration, the loop collapses: ask a question in your messenger, get the answer without leaving the conversation. This is especially valuable for:

Solo developers who want to stay on top of their repos without constant tab-switching
Team leads who need quick PR summaries without reading every line of every diff
Non-technical founders who want visibility into what's happening in their codebase without learning to read code

Setting Up

1.Go to Dashboard → Service Integrations → GitHub
2.Authenticate with your GitHub account (OAuth – no passwords stored)
3.Select which repositories the assistant can access
4.Done – start asking questions from any connected messenger

Five Real Workflows

1. Morning Code Briefing

Set up a morning briefing that includes GitHub activity:

Every morning at 8am, your assistant sends:
- 3 open PRs awaiting review
- 2 new issues opened yesterday
- CI status: all green
- Last deploy: 14 hours ago

This runs automatically via scheduled tasks – no manual check needed.

2. Quick PR Summary

You're in Telegram and a teammate mentions they pushed a PR:

You: "Summarize PR #127"

>

Assistant: "PR #127 adds rate limiting to the /api/search endpoint. Key changes: new RateLimiter middleware (src/middleware/rate-limit.ts), configuration via environment variables (RATE_LIMIT_WINDOW, RATE_LIMIT_MAX), and integration tests. 3 files changed, 142 additions."

Instead of opening GitHub, navigating to the PR, and scanning the diff, you get the summary in 10 seconds.

3. Security-Focused Review

You: "Review PR #127 for security issues"

>

Assistant: "Two observations: (1) The rate limit window is configurable via env var but has no validation – a misconfigured value of 0 would disable rate limiting. Consider adding a minimum bound. (2) The rate limit key uses IP address only – behind a proxy, all users share one limit. Check if X-Forwarded-For is handled."

Not a replacement for thorough code review, but a useful first pass that catches common patterns.

4. Issue Creation from Chat

You notice a bug while chatting with a client:

You: "Create a GitHub issue: login page shows 500 error when user has special characters in their email. Repo: frontend. Label: bug, priority-high"

>

Assistant: "Issue #89 created in frontend: 'Login 500 error with special characters in email' – labeled bug, priority-high."

No context switch. The issue is in GitHub with proper formatting by the time you finish the conversation.

5. Repository Activity Digest

You: "What changed in the API repo this week?"

>

Assistant: "This week: 12 commits across 4 PRs. Major changes: payment webhook handler refactored (PR #124, merged Tuesday), new /v2/users endpoint (PR #125, merged Thursday), CI pipeline updated to Node 20 (PR #126, merged Friday). 1 open PR: #127 (rate limiting, awaiting review). 3 new issues, 2 closed."

Useful for weekly standups or catching up after time off.

How It Compares

Amplify GitHubGitHub CopilotCodeRabbit
What it doesRepo awareness from your messengerCode completion in IDEAutomated PR review
Where it worksTelegram, WhatsApp, Discord, SlackVS Code, JetBrains, etc.GitHub PR comments
PR summariesYes (on demand)NoYes (automatic)
Code reviewYes (conversational)NoYes (automated comments)
Issue creationYes (from chat)NoNo
Activity digestYes (daily/weekly)NoNo
Code completionNoYes (core feature)No
Debugging helpNoYesNo

These tools complement each other. Copilot helps you write code. CodeRabbit reviews PRs automatically. Amplify gives you repo awareness from your messenger – different problems, different solutions.

Frequently Asked Questions

By default, it can create issues and comments. It cannot push code, merge PRs, or modify repository settings. You control the permission scope during GitHub OAuth setup.

Yes. You authorize specific repositories during setup. The assistant only accesses repos you explicitly grant permission to.

The GitHub integration itself is free – GitHub API access is included in the platform fee. The only cost is LLM processing for summarizing, reviewing, and generating responses (~$0.003–$0.01 per interaction).

Currently GitHub only. GitLab and Bitbucket are not currently supported – we're evaluating demand.

For setup instructions, visit [getamplify.team/github-setup](https://getamplify.team/github-setup). The GitHub skill is available to all Amplify users.

Playbook
Enjoyed this Field Note?

Read more