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.
来源信息
- 仓库
- OpenHands/OpenHands-CLI
- 最近来源活动
- 2026年5月7日 19:51
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 263
- 分支
- 120
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- 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:
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`.
3. 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.
在 GitHub 查看