@willbooster/agent-skills 1.17.1 → 1.17.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@willbooster/agent-skills",
-  "version": "1.17.1",
+  "version": "1.17.3",
   "description": "A collection of agent skills for WillBooster Inc.",
   "repository": {
     "type": "git",

package/skills/complete-pr/SKILL.md

@@ -3,30 +3,29 @@ name: complete-pr
 description: Complete GitHub pull requests by iterating on CI and review feedback until the PR is ready.
 ---
 
-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.
+Read the PR body and its messages using the `fetch-pr` skill.
+Then, merge the latest remote `main` branch into the current branch fixing any conflicts.
+After that, 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
 
-1. Read the PR body and its messages using the `fetch-pr` skill.
-2. Check the CI (GitHub Actions) results using the `check-pr-ci` skill.
-3. If any workflow has failed, fix the CI issues, commit, push, and then return to step 2. Otherwise, proceed to step 4.
-4. Fetch unresolved review threads using the `manage-pr-review-threads` skill.
-5. 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.
-6. Address valid review comments by updating the code. For invalid comments, add explanatory comments to the code detailing why the existing implementation is necessary.
+1. Check the CI (GitHub Actions) results using the `check-pr-ci` skill.
+2. If any workflow has failed, fix the CI issues, commit, push, and then 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.
-7. Reply to all review threads using the `manage-pr-review-threads` skill.
-8. If you made changes in step 6, commit and push them, post `/gemini review` on the PR, wait for 5 minutes (`sleep 5m`), and return to step 2.
-9. Update the PR title and body using the `update-pr` skill to reflect all changes.
+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
 
-1. Read the PR body and its messages with the `fetch-pr` skill.
-2. Check the results of CI (GitHub Actions) with the `check-pr-ci` skill.
-3. If any workflow has failed, fix the CI issues, commit, push, and then return to step 2. Otherwise, go to step 4.
-4. Fetch unresolved review threads.
-5. 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.
-6. 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 2.
+1. Check the results of CI (GitHub Actions) with the `check-pr-ci` skill.
+2. If any workflow has failed, fix the CI issues, commit, push, and then return to step 1. Otherwise, proceed to the next step.
+3. Fetch unresolved review threads.
+4. 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.
+5. If there are valid review comments to address, make only the changes supported by the validation from step 4, commit, push, and then return to step 1.
    - Do not post any message like review replies on non-WillBooster repositories.
-7. Update the PR title and body with the `update-pr` skill to reflect all the changes.
+6. Update the PR title and body with the `update-pr` skill to reflect all the changes.

package/skills/wbfy/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wbfy
-description: Apply `wbfy` to the current repository.
+description: Apply `wbfy` to the current (target) repository.
 allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*), Bash(yarn:*)
 ---
 
@@ -8,7 +8,7 @@ allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*), Bash(yarn:*)
 
 1. If the current branch is `main`, create and switch to a new branch from the latest remote `main` branch.
    - Make sure the branch is derived from the latest remote `main` branch to avoid merge conflicts when opening a PR.
-2. Run `yarn start <directory_path_of_target_repo>` in `~/ghq/github.com/WillBooster/wbfy`.
+2. Run `yarn start <root_path_of_target_repo>` in `~/ghq/github.com/WillBooster/wbfy`.
 3. Run `yarn check-for-ai` or `bun check-for-ai` in the target repository (do not run this in `wbfy`).
 4. If any checks fail, do one of the following:
    - Fix the issues in the target repository, then return to step 2.