complete-pr

Original：🇺🇸 English

Translated

Complete GitHub pull requests by iterating on CI and review feedback until the PR is ready.

4installs

Added on2026-03-31

NPX Install

npx skill4agent add willbooster/agent-skills complete-pr

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

or

WillBoosterLab

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

Workflow for

WillBooster

or

WillBoosterLab

repositories

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.

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.