plugins/onboarding/skills/setup-pr-review/SKILL.md
Set 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.
npx skillsauth add openhands/skills setup-pr-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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
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.
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 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.devIf 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.
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)
review-this label or request openhands-agent as reviewer.opened and ready_for_review to
on.pull_request.types and matching conditions to the if: 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.
tools
Iterate on a GitHub pull request — drive it through CI, code review, and QA until it is merge-ready. Poll verification layers with `gh` CLI, diagnose and fix CI failures, address review feedback, retry flaky checks, push fixes, and repeat. The agent is the orchestration loop.
development
Guides technical explanations toward flowing, direct, conversational prose. This skill should be used for engineering chat, design discussion, architecture analysis, code-review explanations, and technical recommendations that should be concise without becoming fragmented or vague.
tools
This skill should be used when the user asks to "set up a Jira automation to create pull requests", "poll Jira for create-pr issues", "automatically create GitHub PRs from Jira tickets", "deploy a Jira issue-to-PR automation", "create a Jira to GitHub PR workflow", or mentions automating GitHub PR creation from a Jira label. Deploys a cron-based OpenHands automation that watches a Jira Cloud project for issues labeled with a configurable label (default: "create-pr") and spawns an agent conversation to create a GitHub pull request for each new issue found. The target GitHub repository is read from the body of the Jira ticket - no repo parameter is required at deploy time.
tools
This skill should be used when the user asks to "create an automation", "schedule a task", "set up a cron job", "webhook integration", "event-triggered automation", or mentions automations, scheduled tasks, cron scheduling, or webhook events in OpenHands Cloud.