SkillsAdd

openhands/openhands-cli · Archived

custom-codereview-guide

>- Repository-specific code review guidelines for OpenHands CLI. Loaded alongside the code-review skill to provide project-specific context and review policies.

First seen Jun 20, 2026

Installation

$ npx skills add openhands/openhands-cli --skill custom-codereview-guide
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

cli-release Same source
openhands/openhands-cli

>- This skill should be used when the user asks to "release the CLI", "prepare a CLI release", …

1 installs
clerk-custom-ui Similar · more installs
clerk/skills

Custom authentication flows and component appearance - hooks (useSignIn, useSignUp), themes, co…

41.3K installs
persona-customer-support Similar · more installs
googleworkspace/cli

Manage customer support — track tickets, respond, escalate issues.

27K installs
shopify-custom-data Similar · more installs
shopify/shopify-ai-toolkit

MUST be used first when prompts mention Metafields or Metaobjects.

10.2K installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from openhands/openhands-cli.

npx skills add openhands/openhands-cli
cli-release 1

Browse all from openhands/openhands-cli

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 205
License LICENSE
Default branch main
Open issues 12
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,624 B
  • docs SUMMARY.md 188 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

OpenHands CLI — Custom Code Review Guidelines

Version Bump PRs — Auto-Approve Policy

When a PR exclusively bumps SDK package versions (e.g., openhands-sdk, openhands-tools, or other OpenHands SDK packages), always approve it by submitting an actual GitHub approval review via the API.

Detection criteria — the PR satisfies all of the following:

  1. The title or branch name contains "bump", "version bump", or "sdk" version references.
  2. The diff only touches dependency-related files (pyproject.toml, uv.lock)

with version number changes for openhands-sdk and/or openhands-tools.

  1. No application source code, tests, configuration, or workflow files are modified.

When these criteria are met:

  • Skip the full code review analysis (data structures, complexity, pragmatism, etc.).
  • Do not require an Evidence section in the PR description.
  • Assign 🟢 Good taste and 🟢 LOW risk.
  • Submit an APPROVE review via the GitHub API (not just a comment). Use:

``bash gh api repos/{owner}/{repo}/pulls/{pr_number}/reviews \ -f event="APPROVE" \ -f body="✅ SDK version bump looks correct. Auto-approved." ` Do NOT merely comment that the PR is "approved" or "ready to merge" — you MUST use the GitHub Pull Request Reviews API with event: "APPROVE"` so the PR actually receives a green approval checkmark.