@willbooster/agent-skills 1.23.2 → 1.23.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@willbooster/agent-skills",
-  "version": "1.23.2",
+  "version": "1.23.4",
   "description": "A collection of agent skills for WillBooster Inc.",
   "repository": {
     "type": "git",
@@ -45,11 +45,11 @@
     "@semantic-release/release-notes-generator": "14.1.0",
     "@tsconfig/bun": "1.0.10",
     "@types/bun": "1.3.13",
-    "@typescript/native-preview": "7.0.0-dev.20260503.1",
+    "@typescript/native-preview": "7.0.0-dev.20260421.2",
     "@willbooster/oxfmt-config": "1.2.2",
     "@willbooster/oxlint-config": "1.4.6",
-    "@willbooster/wb": "13.12.14",
-    "build-ts": "17.1.10",
+    "@willbooster/wb": "13.12.16",
+    "build-ts": "17.1.13",
     "conventional-changelog-conventionalcommits": "9.3.1",
     "lefthook": "2.1.6",
     "oxfmt": "0.48.0",

package/skills/complete-pr/references/willbooster-workflow.md

@@ -5,5 +5,5 @@
 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.
+7. If you made changes in step 5, commit and push them, post `/gemini review` on the PR, wait for 5 minutes (`sleep 300 && echo done`), and return to step 1.
 8. Update the PR title and body using the `update-pr` skill to reflect all changes.

package/skills/wbfy/SKILL.md

@@ -7,14 +7,15 @@ allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*), Bash(yarn:*)
 # wbfy application workflow
 
 1. If the current branch is `main`, create and switch to a new branch based on the latest remote `main` branch.
-   - Ensure the new branch is derived from the latest remote `main` branch to prevent merge conflicts when opening a pull request (PR).
-2. Run `yarn start <root_path_of_target_repo>` inside `~/ghq/github.com/WillBooster/shared/packages/wbfy`.
-3. Run either `yarn verify` or `bun verify` in the target repository (do not run this within the `wbfy` directory).
-4. If any checks fail, resolve them using one of the following methods:
+   - Ensure the new branch is derived from the latest remote `main` branch to prevent merge conflicts when opening a pull request.
+2. Update `~/ghq/github.com/WillBooster/shared/packages/wbfy` (a git repository) to the latest `main` branch.
+3. Run `yarn start <root_path_of_target_repo>` in `~/ghq/github.com/WillBooster/shared/packages/wbfy`.
+4. Run `yarn verify` or `bun verify` in the target repository (not within the `wbfy` directory).
+5. If any checks fail, resolve them using one of the following methods:
    - If the failure originates in the target repository (e.g., existing code violates new linter rules), fix the issue there, commit and push the changes, then return to step 3.
    - If the failure is caused by configuration files modified by `wbfy` (e.g., a `wbfy`-edited `tsconfig.json` does not match the target repository), fix the issue in the `wbfy` directory, commit and push the changes, open a PR in the `wbfy` repository, then return to step 2.
      - Ensure `wbfy` generates the correct configuration files without manual adjustments, as all projects rely on its automation.
      - Avoid ad-hoc hotfixes; prefer general and versatile solutions applicable to all projects.
      - Add comments to the `wbfy` codebase to clarify the reasoning behind your fixes.
-5. Commit and push the applied changes to the target repository, then run either the `open-pr` or `update-pr` skill.
+6. Commit and push the applied changes to the target repository, then run either the `open-pr` or `update-pr` skill.
    - Since `wbfy` creates, modifies, and deletes multiple files in the target repository, verify that all changes are included in your commit.