@willbooster/agent-skills 1.21.10 → 1.21.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@willbooster/agent-skills",
-  "version": "1.21.10",
+  "version": "1.21.12",
   "description": "A collection of agent skills for WillBooster Inc.",
   "repository": {
     "type": "git",
@@ -18,8 +18,6 @@
   ],
   "scripts": {
     "build": "build-ts app --input src/cli.ts && chmod +x dist/cli.js",
-    "check-all-for-ai": "bun run check-for-ai && bun run test",
-    "check-for-ai": "bun install > /dev/null && bun run cleanup",
     "cleanup": "bun --bun wb lint --fix --format",
     "format": "bun --bun wb lint --format",
     "install-skills": "bunx skills@latest add ./ --skill '*' --agent claude-code --agent codex --agent gemini-cli --yes",
@@ -46,12 +44,12 @@
     "@semantic-release/npm": "13.1.5",
     "@semantic-release/release-notes-generator": "14.1.0",
     "@tsconfig/bun": "1.0.10",
-    "@types/bun": "1.3.12",
+    "@types/bun": "1.3.13",
     "@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.8",
-    "build-ts": "17.1.8",
+    "@willbooster/wb": "13.12.10",
+    "build-ts": "17.1.10",
     "conventional-changelog-conventionalcommits": "9.3.1",
     "lefthook": "2.1.6",
     "oxfmt": "0.47.0",

package/skills/refactor-structure/SKILL.md

@@ -5,10 +5,13 @@ description: Refactor the source tree by splitting oversized files, grouping rel
 
 # Structure refactor workflow
 
-1. Inspect the current layout using `tree -h src` (or `tree -h <specified_dir>`) to identify structural issues such as oversized files, mixed responsibilities, misplaced modules, unclear names, and duplicated organization patterns.
+1. Inspect the current layout using the following commands to identify structural issues, such as oversized files, mixed responsibilities, misplaced modules, unclear names, and duplicated organization patterns.
+   - `find src -type f -not -path '*/__generated__/*' -print0 | xargs -0 wc -l 2>/dev/null | sort -rn | head -30`
+   - `tree -h src`
+   - If the user specifies a directory, replace `src` with it.
 2. Reorganize the code by responsibility to improve cohesion and reduce coupling.
    - Split oversized files, group related modules, and create new directories only when they clarify ownership.
-   - Update imports alongside your changes maintaining existing behavior.
+   - Update imports alongside your changes while maintaining existing behavior.
 3. Rename files and identifiers (such as variables and functions) to more accurately reflect their roles.
    - Ensure all references are updated accordingly.
 4. Run the quickest relevant verification tools, such as type checkers or linters, to detect broken imports or incorrect module wiring.

package/skills/update-deps/SKILL.md

@@ -9,8 +9,8 @@ allowed-tools: Bash(bun:*), Bash(bunx:*), Bash(gh:*), Bash(git:*), Bash(yarn:*)
 1. Update all dependencies, including subpackages, from the repository root.
    - For Yarn projects, run `yarn up '**'`.
    - For Bun projects, run `bunx @willbooster/agent-skills@latest update-bun-deps`.
-2. Run either `yarn check-for-ai` or `bun check-for-ai`.
-3. Fix any issues reported by the `check-for-ai` command.
+2. Run either `yarn verify` or `bun verify`.
+3. Fix any issues reported by the `verify` command.
    - For updating Vitest, see https://raw.githubusercontent.com/WillBooster/shared/refs/heads/main/packages/wb/vitest.config.ts
    - For other issues, refer to the latest official documentation.
 4. Check whether each updated dependency is still required for the project.

package/skills/wbfy/SKILL.md

@@ -9,7 +9,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 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 check-for-ai` or `bun check-for-ai` in the target repository (do not run this within the `wbfy` directory).
+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:
    - 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.