setup-pr-review
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.
What this skill does
# Set Up OpenHands PR 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-20250929` - `llm-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-this` label or request `openhands-agent` as reviewer. - Automatic: review every new PR. Add `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.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.