@willbooster/agent-skills 1.17.3 → 1.18.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@willbooster/agent-skills",
-  "version": "1.17.3",
+  "version": "1.18.0",
   "description": "A collection of agent skills for WillBooster Inc.",
   "repository": {
     "type": "git",
@@ -48,10 +48,10 @@
     "@types/bun": "1.3.11",
     "@willbooster/biome-config": "3.4.1",
     "@willbooster/prettier-config": "10.4.0",
-    "@willbooster/wb": "13.5.2",
+    "@willbooster/wb": "13.7.0",
     "build-ts": "17.0.22",
     "conventional-changelog-conventionalcommits": "9.3.0",
-    "lefthook": "2.1.4",
+    "lefthook": "2.1.5",
     "prettier": "3.8.1",
     "prettier-plugin-java": "2.8.1",
     "semantic-release": "25.0.3",

package/skills/complete-pr/SKILL.md

@@ -4,7 +4,7 @@ description: Complete GitHub pull requests by iterating on CI and review feedbac
 ---
 
 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.
+Then, merge the latest remote `main` branch into the current branch fixing any conflicts and push it.
 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.
 

package/skills/fetch-issue/SKILL.md

@@ -4,6 +4,4 @@ description: Fetch a GitHub issue body and its messages for the current reposito
 allowed-tools: Bash(bun:*), Bash(gh:*)
 ---
 
-# Fetch GitHub Issue Messages
-
 Run the following command to fetch the issue body and its messages: `bunx @willbooster/agent-skills@latest fetch-issue <issue-number-or-url>`

package/skills/fetch-pr/SKILL.md

@@ -4,6 +4,4 @@ description: Fetch a GitHub pull request body and its messages for the current r
 allowed-tools: Bash(bun:*), Bash(gh:*)
 ---
 
-# Fetch GitHub PR Messages
-
 Run the following command to fetch the pull request body and messages, excluding inline review comments: `bunx @willbooster/agent-skills@latest fetch-pr <pr-number-or-url>`

package/skills/fix-bug/SKILL.md

@@ -19,3 +19,4 @@ description: Fix a reported bug by first enhancing tests until the bug is reprod
 6. Run the enhanced tests and confirm they pass with the fix in place.
 7. If the repository workflow requires broader verification, run the relevant checks after the targeted tests pass.
 8. Summarize the root cause, the test enhancement, and the implementation fix.
+9. Commit and push the changes, then run either the `open-pr` or `update-pr` skill.

package/skills/open-pr/SKILL.md

@@ -13,7 +13,7 @@ Run the following command to open a pull request.
 Finally, report the PR URL.
 
 ```bash
-bunx @willbooster/agent-skills@latest open-pr <<'EOF'
+bunx @willbooster/agent-skills@latest open-pr "feat: concise PR title" <<'EOF'
 Close #<issue>
 
 ## Summary
@@ -37,3 +37,16 @@ Close #<issue>
 - Breaking changes, rollout concerns, screenshots, or follow-up work
 EOF
 ```
+
+Note that the prefix of the PR title must follow the Conventional Commits specification:
+
+- feat: A new feature for the user or API.
+- fix: A bug fix for the user or API.
+- build: Changes that affect the build system or external dependencies (e.g., npm, webpack, typescript).
+- chore: Routine tasks, maintenance, or tooling changes that don't modify source or test files.
+- ci: Changes to CI/CD configuration files and scripts.
+- docs: Documentation-only changes.
+- perf: A code change that improves performance.
+- refactor: A code change that neither fixes a bug nor adds a feature, but improves code structure or readability.
+- style: Changes that do not affect the meaning of the code (e.g., formatting).
+- test: Adding missing tests or correcting existing tests.

package/skills/refactor-structure/SKILL.md

@@ -9,4 +9,5 @@ description: Refactor the source tree by splitting oversized files, grouping rel
 2. Reorganize by responsibility to improve cohesion and reduce coupling: split oversized files, group related modules, and add directories only when they make ownership clearer.
 3. Update imports as you go and preserve existing behavior unless broader changes are explicitly requested.
 4. Run the lightest relevant verification, such as typecheck or lint, to catch broken imports or module wiring.
-5. Summarize what moved and why the new structure is easier to maintain.
+5. Commit and push the changes, then run either the `open-pr` or `update-pr` skill.
+6. Summarize what moved and why the new structure is easier to maintain.

package/skills/update-pr/SKILL.md

@@ -7,34 +7,11 @@ allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*)
 # Update PR workflow
 
 Write the full replacement pull request title and the complete replacement PR body so they reflect the current scope, motivation, and validation.
-Run `update-pr-title` first, then run `update-pr-body`.
+Run `update-pr` with the title as the first argument and the body on stdin.
 Finally, report the pull request URL.
 
-## Update the PR title
-
-```bash
-bunx @willbooster/agent-skills@latest update-pr-title <<'EOF'
-feat: concise PR title
-EOF
-```
-
-Note that the prefix of the PR title must follow the Conventional Commits specification:
-
-- feat: A new feature for the user or API.
-- fix: A bug fix for the user or API.
-- build: Changes that affect the build system or external dependencies (e.g., npm, webpack, typescript).
-- chore: Routine tasks, maintenance, or tooling changes that don't modify source or test files.
-- ci: Changes to CI/CD configuration files and scripts.
-- docs: Documentation-only changes.
-- perf: A code change that improves performance.
-- refactor: A code change that neither fixes a bug nor adds a feature, but improves code structure or readability.
-- style: Changes that do not affect the meaning of the code (e.g., formatting).
-- test: Adding missing tests or correcting existing tests.
-
-## Update the PR body
-
 ```bash
-bunx @willbooster/agent-skills@latest update-pr-body <<'EOF'
+bunx @willbooster/agent-skills@latest update-pr "feat: concise PR title" <<'EOF'
 Close #<issue>
 
 ## Summary
@@ -58,3 +35,16 @@ Close #<issue>
 - Breaking changes, rollout concerns, screenshots, or follow-up work
 EOF
 ```
+
+Note that the prefix of the PR title must follow the Conventional Commits specification:
+
+- feat: A new feature for the user or API.
+- fix: A bug fix for the user or API.
+- build: Changes that affect the build system or external dependencies (e.g., npm, webpack, typescript).
+- chore: Routine tasks, maintenance, or tooling changes that don't modify source or test files.
+- ci: Changes to CI/CD configuration files and scripts.
+- docs: Documentation-only changes.
+- perf: A code change that improves performance.
+- refactor: A code change that neither fixes a bug nor adds a feature, but improves code structure or readability.
+- style: Changes that do not affect the meaning of the code (e.g., formatting).
+- test: Adding missing tests or correcting existing tests.

package/skills/wbfy/SKILL.md

@@ -6,12 +6,12 @@ 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 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 <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.
-   - If the failure originates from `wbfy`, fix `~/ghq/github.com/WillBooster/wbfy`, commit and push the changes, open a PR in the `wbfy` repository, then return to step 1.
-5. Commit and push any changes in the target repository, then open a PR.
-   - `wbfy` creates, modifies, and deletes many files in the target repository, so be sure to include all of them in the commit.
+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/wbfy`.
+3. Run either `yarn check-for-ai` or `bun check-for-ai` 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:
+   - 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, and 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 `~/ghq/github.com/WillBooster/wbfy`, commit and push the changes, open a PR in the `wbfy` repository, and then return to step 2.
+5. 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.