setup-openhands
Set up a repository for effective use with OpenHands. Creates AGENTS.md, setup and pre-commit scripts, and a PR review workflow. Designed to run automatically with minimal user intervention. Use when a user wants to configure their repo for OpenHands.
What this skill does
# Set Up OpenHands for a Repository Work through these steps in order. ## Step 1: Create AGENTS.md Run `setup-agents-md` to generate a root-level `AGENTS.md` from the repo's actual CI workflows, build files, and documentation. ## Step 2: Create `.openhands/setup.sh` Create `.openhands/setup.sh` — a bootstrap script that runs at the start of every OpenHands session. Read the repo's CI workflows, AGENTS.md, and build files to determine the correct commands. The script should: - Install dependencies (the project's actual install command) - Set required environment variables - Run any other bootstrap steps (e.g. copy `.env.example` to `.env`) Keep it idempotent and fast. Use the real commands from CI, not generic examples. **Docs**: https://docs.openhands.dev/openhands/usage/customization/repository#setup-script ## Step 3: Create `.openhands/pre-commit.sh` Create `.openhands/pre-commit.sh` — runs before every commit OpenHands makes. Read the repo's CI workflows to find the lint and test commands, then mirror them in the script. Exit non-zero on failure so the agent gets immediate feedback instead of waiting for CI. The script should run the same checks CI runs — if CI runs `ruff check` and `pytest`, run those. If it runs `cargo clippy` and `cargo test`, run those. **Docs**: https://docs.openhands.dev/openhands/usage/customization/repository#pre-commit-script ## Step 4: Set up PR review Run `setup-pr-review` to create the GitHub Actions workflow and walk the user through configuration. ## Step 5: Verify Confirm all files exist and are correct: - `AGENTS.md` at repo root with real commands (not boilerplate) - `.openhands/setup.sh` with the project's actual install/bootstrap commands - `.openhands/pre-commit.sh` mirroring the CI lint/test checks - `.github/workflows/pr-review.yml` with valid YAML
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.