@willbooster/agent-skills 1.26.0 → 1.27.0

package/README.md

@@ -23,6 +23,7 @@ bunx skills@latest add WillBooster/agent-skills --agent claude-code --agent code
 
 | Skill                                                                                                                                                                                                                             | Uses Subagent | Purpose                                                    | Example Prompt (`$<skill_name>` for Codex CLI, `/<skill_name>` for Claude Code) |
 | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ---------------------------------------------------------- | ------------------------------------------------------------------------------- |
+| [`check-pkg-preflight`](skills/check-pkg-preflight/SKILL.md)                                                                                                                                                                      | No            | Investigate and fix pkg-preflight CI failures.             | `$check-pkg-preflight`                                                          |
 | [`check-pr-ci`](skills/check-pr-ci/SKILL.md)                                                                                                                                                                                      | No            | Check the latest CI results for the current PR.            | N/A (called internally by [`complete-pr`](skills/complete-pr/SKILL.md))         |
 | [`complete-pr`](skills/complete-pr/SKILL.md)                                                                                                                                                                                      | No            | Finish a PR by handling CI and review feedback.            | `$complete-pr`                                                                  |
 | [`fetch-issue`](skills/fetch-issue/SKILL.md)                                                                                                                                                                                      | No            | Fetch an issue body and messages.                          | `$fetch-issue https://github.com/WillBooster/agent-skills/issues/41`            |
@@ -33,6 +34,7 @@ bunx skills@latest add WillBooster/agent-skills --agent claude-code --agent code
 | [`plan-issue-claude`](skills/plan-issue-claude/SKILL.md) / [`plan-issue-codex`](skills/plan-issue-codex/SKILL.md) / [`plan-issue-gemini`](skills/plan-issue-gemini/SKILL.md)                                                      | Yes           | Generate an implementation plan with a chosen agent.       | `$plan-issue-codex https://github.com/WillBooster/agent-skills/issues/41`       |
 | [`playwright-cli`](skills/playwright-cli/SKILL.md)                                                                                                                                                                                | No            | Automate browser tasks with Playwright CLI.                | `Take a screenshot of ABC page with $playwright-cli`                            |
 | [`refactor-structure`](skills/refactor-structure/SKILL.md)                                                                                                                                                                        | No            | Reorganize the source tree without changing behavior.      | `$refactor-structure`                                                           |
+| [`release`](skills/release/SKILL.md)                                                                                                                                                                                              | No            | Release using the repository's documented workflow.        | `$release`                                                                      |
 | [`review-all`](skills/review-all/SKILL.md) / [`review-claude`](skills/review-claude/SKILL.md) / [`review-codex`](skills/review-codex/SKILL.md) / [`review-gemini`](skills/review-gemini/SKILL.md)                                 | Yes           | Review code and report only still-valid findings.          | `$review-all`                                                                   |
 | [`review-fix-all`](skills/review-fix-all/SKILL.md) / [`review-fix-claude`](skills/review-fix-claude/SKILL.md) / [`review-fix-codex`](skills/review-fix-codex/SKILL.md) / [`review-fix-gemini`](skills/review-fix-gemini/SKILL.md) | Yes           | Review code and fix only still-valid findings.             | `$review-fix-all`                                                               |
 | [`screenshot-claude`](skills/screenshot-claude/SKILL.md) / [`screenshot-codex`](skills/screenshot-codex/SKILL.md) / [`screenshot-gemini`](skills/screenshot-gemini/SKILL.md)                                                      | Yes           | Take a page screenshot with a chosen agent.                | `$screenshot-codex https://example.com "Pricing" "the comparison table"`        |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@willbooster/agent-skills",
-  "version": "1.26.0",
+  "version": "1.27.0",
   "description": "A collection of agent skills for WillBooster Inc.",
   "repository": {
     "type": "git",
@@ -45,15 +45,15 @@
     "@semantic-release/release-notes-generator": "14.1.1",
     "@tsconfig/bun": "1.0.10",
     "@types/bun": "1.3.13",
-    "@typescript/native-preview": "7.0.0-dev.20260510.1",
+    "@typescript/native-preview": "7.0.0-dev.20260511.1",
     "@willbooster/oxfmt-config": "1.2.2",
     "@willbooster/oxlint-config": "1.4.6",
-    "@willbooster/wb": "13.13.1",
-    "build-ts": "17.1.13",
+    "@willbooster/wb": "13.15.0",
+    "build-ts": "17.1.15",
     "conventional-changelog-conventionalcommits": "9.3.1",
     "lefthook": "2.1.6",
-    "oxfmt": "0.49.0",
-    "oxlint": "1.64.0",
+    "oxfmt": "0.50.0",
+    "oxlint": "1.65.0",
     "oxlint-tsgolint": "0.22.1",
     "semantic-release": "25.0.3",
     "sort-package-json": "3.6.1"

package/skills/check-pkg-preflight/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: check-pkg-preflight
+description: Investigate and fix pkg-preflight failures reported by WillBooster reusable workflow CI.
+allowed-tools: Bash(bun:*), Bash(curl:*), Bash(gh:*), Bash(git:*)
+---
+
+Use this skill when CI fails with `pkg-preflight rejected dependency lockfile changes with verdict: fail`.
+
+1. Read the failing job log: `gh run view <run-id> --repo <owner>/<repo> --job <job-id> --log`.
+2. Fetch PR metadata: `gh pr view <pr-number-or-url> --json baseRefOid,headRefOid,files,baseRefName,headRefName,url`.
+3. If the log does not include `json.results`, reproduce the request with the changed lockfiles. Put temporary payloads in `.tmp` or `/tmp`.
+
+   ```bash
+   curl --fail-with-body --max-time 120 --show-error --silent \
+     https://pkg-preflight.up.railway.app/rpc/inspectLockfileDiff \
+     -H 'content-type: application/json' \
+     --data-binary @.tmp/pkg-preflight-request.json
+   ```
+
+4. Inspect `json.results[]` for the failing `name`, `baselineVersion`, `targetVersion`, `riskScore`, and `findings`.
+5. Resolve the failure using one of the following methods:
+   - If the dependency change is genuinely risky, stay in the original repository, fix the PR's dependency update, verify it with that repository's checks, commit and push, then run the `complete-pr` skill.
+   - If it is a false positive or scanner bug, fix `~/ghq/github.com/WillBooster/pkg-preflight`, verify there with focused checks and `bun verify` unless `bun verify-full` is required, run the `complete-pr` skill, and run the `release` skill if the pkg-preflight service must be deployed. Then return to the original repository and re-run the failed CI job, for example with `gh run rerun <run-id> --failed`.
+6. Report the package/version pair, finding, root cause, fix, and verification commands.

package/skills/release/SKILL.md

@@ -0,0 +1,12 @@
+---
+name: release
+description: Release the current repository to production environment.
+allowed-tools: Bash(gh:*), Bash(git:*)
+disable-model-invocation: true
+---
+
+1. Read release-related workflow files first, such as `.github/workflows/deploy.yml`, `.github/workflows/deploy-production.yml`, `.github/workflows/release.yml`. Do not assume that pushing `main` is safe.
+2. Release using the workflow files:
+   - If production deploys from `release`, rebase `release` onto the latest `main`, then push `release`.
+   - Otherwise, follow the workflow files exactly.
+3. Report the deployment trigger, pushed branch or tag, deployment URL, and any command that failed or still needs manual approval.

package/skills/wbfy/SKILL.md

@@ -8,14 +8,18 @@ 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.
-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.
+2. Make sure .env files define NEXT_PUBLIC_BASE_URL correctly, as `wbfy` uses this environment variable to generate configuration files.
+3. Update `~/ghq/github.com/WillBooster/shared/packages/wbfy` (a git repository) to the latest `main` branch.
+4. Run `yarn start <root_path_of_target_repo>` in `~/ghq/github.com/WillBooster/shared/packages/wbfy`.
+5. Run `yarn verify` or `bun verify` in the target repository (not within the `wbfy` directory).
+6. 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 4.
+   - 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 3.
      - 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.
-6. Commit and push the applied changes to the target repository, then run either the `open-pr` or `update-pr` skill.
+7. 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.
+8. Check the CI (GitHub Actions) results using the `check-pr-ci` skill.
+9. If any workflow fails, pull the latest remote changes, resolve the issues, commit, push, and return to step 8. Otherwise, proceed to the next step.
+10. Merge the PR via `gh`.