complete-pr

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use this skill when the goal is to drive a PR to a merge-ready state rather than just inspect it once. First, fetch the current repository owner with

gh repo view --json owner --jq '.owner.login'

. If the owner is

WillBooster

WillBoosterLab

, follow the first workflow below. Otherwise, follow the second workflow below.

当你的目标是推动PR达到可合并状态，而不仅仅是一次性检查时，使用此技能。首先，使用

gh repo view --json owner --jq '.owner.login'

获取当前仓库所有者。如果所有者是

WillBooster

或

WillBoosterLab

，请遵循下方第一个工作流。否则，请遵循下方第二个工作流。

Workflow for

WillBooster

WillBoosterLab

repositories

WillBooster

或

WillBoosterLab

仓库的工作流

Read the PR body and its messages with the
```
fetch-pr
```
skill.
Check the results of CI (GitHub Actions) with the
```
check-pr-ci
```
skill.
If any workflow has failed, fix the CI issues, commit, push, and then return to step 2. Otherwise, go to step 4.
Fetch unresolved review threads with the
```
manage-pr-review-threads
```
skill.
Review each unresolved thread and decide whether it requires a code or documentation change. Validate each claim against the current codebase first, and reproduce it or check official documentation when needed instead of relying on memory. Ignore only comments that are clearly outdated, incorrect, or intentionally declined with solid reasoning.
If there are valid review comments to address, make only the changes supported by the validation from step 5, commit, push, and post
```
/gemini review
```
to the PR.
Reply to all review threads with the
```
manage-pr-review-threads
```
skill.
If you made any changes in step 6, wait for 5 minutes (
```
sleep 5m
```
) then return to step 2. Otherwise, stop.

使用
```
fetch-pr
```
技能读取PR正文及其消息。
使用
```
check-pr-ci
```
技能检查CI（GitHub Actions）的运行结果。
如果有任何工作流运行失败，修复CI问题，提交、推送代码，然后回到第2步。如果没有失败，进入第4步。
使用
```
manage-pr-review-threads
```
技能获取未解决的评审线程。
评审每个未解决的线程，判断是否需要修改代码或文档。首先对照当前代码库验证每条评论的合理性，必要时复现问题或查阅官方文档，不要仅凭记忆判断。仅忽略明显过时、不正确或有充分理由明确拒绝的评论。
如果存在需要处理的有效评审评论，仅实施第5步验证通过的修改，提交、推送代码，并在PR下发布
```
/gemini review
```
评论。
使用
```
manage-pr-review-threads
```
技能回复所有评审线程。
如果你在第6步做了任何修改，等待5分钟（
```
sleep 5m
```
）后回到第2步。否则结束流程。

Read the PR body and its messages with the
```
fetch-pr
```
skill.
Check the results of CI (GitHub Actions) with the
```
check-pr-ci
```
skill.
If any workflow has failed, fix the CI issues, commit, push, and then return to step 2. Otherwise, go to step 4.
Fetch unresolved review threads.
Review each unresolved thread and decide whether it requires a code or documentation change. Validate each claim against the current codebase first, and reproduce it or check official documentation when needed instead of relying on memory. Ignore only comments that are clearly outdated, incorrect, or intentionally declined with solid reasoning.
If there are valid review comments to address, make only the changes supported by the validation from step 5, commit, push, and then return to step 1. Otherwise, stop.
- Do not post any message like review replies on non-WillBooster repositories.

使用
```
fetch-pr
```
技能读取PR正文及其消息。
使用
```
check-pr-ci
```
技能检查CI（GitHub Actions）的运行结果。
如果有任何工作流运行失败，修复CI问题，提交、推送代码，然后回到第2步。如果没有失败，进入第4步。
获取未解决的评审线程。
评审每个未解决的线程，判断是否需要修改代码或文档。首先对照当前代码库验证每条评论的合理性，必要时复现问题或查阅官方文档，不要仅凭记忆判断。仅忽略明显过时、不正确或有充分理由明确拒绝的评论。
如果存在需要处理的有效评审评论，仅实施第5步验证通过的修改，提交、推送代码，然后回到第1步。否则结束流程。
- 不要在非WillBooster的仓库中发布评审回复之类的任何消息。