complete-pr

Use the fetch-pr skill to read the PR body and its messages. Fetch the latest changes from the remote. If the remote default branch has new commits, merge it into the current branch, resolve any conflicts, and push the changes. Next, fetch the current repository owner using the command 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.

Workflow for WillBooster or WillBoosterLab repositories

1. Check the CI (GitHub Actions) results using the check-pr-ci skill.
2. If any workflow fails, pull the latest remote changes, resolve the issues, commit, push, and return to step 1. Otherwise, proceed to the next step.
3. Fetch unresolved review threads using the manage-pr-review-threads skill.
4. Review each unresolved thread to determine if it requires code or documentation changes. Validate each claim against the current codebase first, and reproduce issues or consult official documentation when necessary instead of relying on memory.
5. Address valid review comments by updating the code. For invalid comments, add explanatory comments to the code detailing why the existing implementation is necessary.
   • If there are valid review comments that are out of scope for the current PR, create new issues for them.
6. Reply to all review threads using the manage-pr-review-threads skill.
7. If you made changes in step 5, commit and push them, post /gemini review on the PR, wait for 5 minutes (sleep 5m), and return to step 1.
8. Update the PR title and body using the update-pr skill to reflect all changes.

Workflow for the other repositories