@willbooster/agent-skills 1.20.1 → 1.21.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@willbooster/agent-skills",
-  "version": "1.20.1",
+  "version": "1.21.0",
   "description": "A collection of agent skills for WillBooster Inc.",
   "repository": {
     "type": "git",
@@ -33,7 +33,6 @@
     "test:integration": "RUN_GITHUB_INTEGRATION=1 bun test test/cli/agentSkillsCli.e2e.test.ts",
     "typecheck": "bun --bun wb typecheck"
   },
-  "prettier": "@willbooster/prettier-config",
   "dependencies": {
     "commander": "14.0.3",
     "minimatch": "10.2.5",
@@ -46,19 +45,16 @@
     "@semantic-release/release-notes-generator": "14.1.0",
     "@tsconfig/bun": "1.0.10",
     "@types/bun": "1.3.12",
-    "@typescript/native-preview": "7.0.0-dev.20260417.1",
+    "@typescript/native-preview": "7.0.0-dev.20260418.1",
     "@willbooster/oxfmt-config": "1.2.1",
     "@willbooster/oxlint-config": "1.4.4",
-    "@willbooster/prettier-config": "10.4.0",
-    "@willbooster/wb": "13.11.5",
-    "build-ts": "17.1.0",
+    "@willbooster/wb": "13.11.8",
+    "build-ts": "17.1.6",
     "conventional-changelog-conventionalcommits": "9.3.1",
     "lefthook": "2.1.5",
     "oxfmt": "0.45.0",
     "oxlint": "1.60.0",
     "oxlint-tsgolint": "0.21.0",
-    "prettier": "3.8.2",
-    "prettier-plugin-java": "2.8.1",
     "semantic-release": "25.0.3",
     "sort-package-json": "3.6.1"
   },

package/skills/complete-pr/SKILL.md

@@ -11,7 +11,7 @@ If the owner is `WillBooster` or `WillBoosterLab`, follow the first workflow bel
 ## Workflow for `WillBooster` or `WillBoosterLab` repositories
 
 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.
+2. If any workflow fails, pull the latest remote changes, resolve the issues, commit, push, and 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.
@@ -22,10 +22,10 @@ If the owner is `WillBooster` or `WillBoosterLab`, follow the first workflow bel
 
 ## Workflow for the other repositories
 
-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.
+1. Check the CI (GitHub Actions) results using the `check-pr-ci` skill.
+2. If any workflow fails, pull the latest remote changes, resolve the issues, commit, push, and 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 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.
-6. Update the PR title and body with the `update-pr` skill to reflect all the changes.
+6. Update the PR title and body using the `update-pr` skill to reflect all changes.