custom-codereview-guide

Sterne213

Forks106

Aktualisiert7. Mai 2026 um 19:51

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

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

OpenHands

OpenHands/OpenHands-CLI

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

cli-release

OpenHands/OpenHands-CLI

This skill should be used when the user asks to "release the CLI", "prepare a CLI release", "publish a new CLI version", "cut a CLI release", "do a release", "bump the CLI version", or mentions the CLI release checklist or release process. Guides through the full OpenHands CLI release workflow from version bump to binary publication, emphasizing human checkpoints.

2026-04-06213

name	custom-codereview-guide
description	Repository-specific code review guidelines for OpenHands CLI. Loaded alongside the code-review skill to provide project-specific context and review policies.
triggers	["/codereview"]

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:

The title or branch name contains "bump", "version bump", or "sdk" version references.
The diff only touches dependency-related files (pyproject.toml, uv.lock) with version number changes for openhands-sdk and/or openhands-tools.
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:
```
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.