Set Up OpenHands PR Review
SkillFiles & storageSet up the OpenHands automated PR review workflow in a GitHub repository. Creates the workflow file and asks the user for configuration preferences. Use when a user wants AI code review on their pull requests.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Set Up OpenHands PR Review skill
What this skill tells your AI
The instructions your AI receives, as published by openhands/extensions in plugins/onboarding/skills/setup-pr-review/SKILL.md and read by ahel’s review.
Add the PR review workflow to a GitHub repository so an OpenHands agent can review pull requests and post inline comments.
Docs: https://docs.all-hands.dev/sdk/guides/github-workflows/pr-review
Step 1: Create the workflow file
Create .github/workflows/pr-review.yml in the target repo. Fetch the latest
example from https://docs.all-hands.dev/sdk/guides/github-workflows/pr-review
and use it as the starting template. The workflow calls the
OpenHands/extensions/plugins/pr-review composite action directly.
Step 2: Configure the LLM
Ask the user whether they are using the OpenHands app (app.all-hands.dev) or their own LLM provider (e.g. Anthropic, OpenAI directly).
OpenHands app (default)
OpenHands app users already have access to an LLM API key through the OpenHands litellm proxy. Tell them:
Go to https://app.all-hands.dev → Account → API Keys → OpenHands LLM Key, and copy your key. Then add it as a GitHub repository secret: Settings → Secrets and variables → Actions → New repository secret. Name it
LLM_API_KEY.
Set these inputs in the workflow with: block:
llm-model: litellm_proxy/claude-sonnet-4-5-20250929llm-base-url: https://llm-proxy.app.all-hands.dev
Own LLM provider
If the user has their own API key (e.g. from Anthropic or OpenAI), tell them
to add it as a repository secret named LLM_API_KEY using the same path
above. Leave llm-base-url unset and set llm-model to the provider-prefixed
model name (e.g. anthropic/claude-sonnet-4-5-20250929).
You cannot create secrets — the user must do it manually. Do not ask for the key value. Just tell them where to put it.
Step 3: Ask the user for preferences
Present these options and apply any requested changes to the workflow file:
Review style (default: roasted)
roasted— Linus Torvalds-style, blunt, focuses on data structures and simplicity.standard— balanced, covers style/readability/security.
When to trigger (default: on-demand only)
- On-demand: add
review-thislabel or requestopenhands-agentas reviewer. - Automatic: review every new PR. Add
openedandready_for_reviewtoon.pull_request.typesand matching conditions to theif:block.
After applying these, ask the user if they want to explore additional options (model selection, evidence requirements, custom review skills, observability). If yes, walk them through it — use the docs as a reference: https://docs.all-hands.dev/sdk/guides/github-workflows/pr-review If not, you're done.
Signals
- GitHub stars
- 144
- Forks
- 86
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
setup-pr-review- Source
- github.com/openhands/extensions