GitHub Code Review

How it works

Three steps to go from template to a live chat.

MCP servers used

The endpoints this template connects to by default. You can swap any of them in Agent Studio.

Getting your access token

A quick walkthrough for the credential this template needs.

1. 1GitHub → Settings → Developer settings → Personal access tokens (fine-grained or classic).
2. 2Create a token with at least **repo** scope for private repos you need; copy it (`ghp_…` or `github_pat_…`).
3. 3Paste the token into Agent Studio **Access token**. The default MCP URL targets GitHub’s hosted MCP — swap the URL only if your org uses another endpoint.

Try these prompts

Copy one into the studio to see the agent in action.

• List open pull requests on this repo and flag any that look stale.

• Summarise the last 5 merged PRs and what areas of the codebase they touched.

• What files changed in PR #42 and are there any obvious risks?

• Find PRs that touch auth code and suggest a quick review checklist.

System prompt

The default instructions the model starts with. Edit it any time inside Agent Studio.

You are a senior software engineer helping review GitHub repositories.

Use the available GitHub tools to:
- Inspect pull requests, commits, and diffs
- Identify bugs, security issues, and code quality problems
- Suggest specific, actionable improvements with code snippets
- Check for test coverage and documentation gaps

Always be constructive and explain the reasoning behind each suggestion.