@willbooster/agent-skills 1.28.5 → 1.28.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (9) hide show
  1. package/dist/cli.js +2 -2
  2. package/package.json +2 -2
  3. package/skills/open-pr/SKILL.md +13 -5
  4. package/skills/review-fix-all/SKILL.md +1 -1
  5. package/skills/review-fix-claude/SKILL.md +1 -1
  6. package/skills/review-fix-codex/SKILL.md +1 -1
  7. package/skills/review-fix-gemini/SKILL.md +1 -1
  8. package/skills/update-pr/SKILL.md +13 -4
  9. package/skills/wbfy/SKILL.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@willbooster/agent-skills",
3
- "version": "1.28.5",
3
+ "version": "1.28.7",
4
4
  "description": "A collection of agent skills for WillBooster Inc.",
5
5
  "repository": {
6
6
  "type": "git",
@@ -48,7 +48,7 @@
48
48
  "@typescript/native-preview": "7.0.0-dev.20260518.1",
49
49
  "@willbooster/oxfmt-config": "1.2.2",
50
50
  "@willbooster/oxlint-config": "1.4.6",
51
- "@willbooster/wb": "13.19.4",
51
+ "@willbooster/wb": "13.19.7",
52
52
  "build-ts": "17.1.15",
53
53
  "conventional-changelog-conventionalcommits": "9.3.1",
54
54
  "lefthook": "2.1.6",
package/skills/open-pr/SKILL.md CHANGED
@@ -8,7 +8,9 @@ allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*)
8
8
 
9
9
  Commit and push any local changes to the current branch.
10
10
  Write a PR body that helps reviewers quickly understand the scope, motivation, and validation.
11
- Include the linked issue when applicable, a concise summary of the changes, the reasoning behind them, and how they were tested.
11
+ Include the linked issue when applicable, both customer-facing and technical summaries, the reasoning behind the changes, and how they were tested.
12
+ Write the customer-facing summary for non-technical readers who know nothing about the internal implementation and only need to understand specification, behavior, workflow, or user-visible impact.
13
+ Write the technical summary for engineers who want to understand code, architecture, dependencies, and implementation scope.
12
14
  Run the following command to open a pull request.
13
15
  Finally, report the PR URL.
14
16
 
@@ -16,11 +18,17 @@ Finally, report the PR URL.
16
18
  bunx @willbooster/agent-skills@latest open-pr "feat: concise PR title" <<'EOF'
17
19
  Close #<issue>
18
20
 
19
- ## Summary
21
+ ## Customer Summary
20
22
 
21
- - What changed
22
- - Key scope or affected area
23
- - Any notable tradeoff or limitation
23
+ - Specification, behavior, workflow, or user-visible changes
24
+ - Impact on customers, operators, or internal users
25
+ - Rollout, compatibility, or migration notes in non-technical language
26
+
27
+ ## Technical Summary
28
+
29
+ - Code, configuration, dependency, or architecture changes
30
+ - Key implementation scope or affected modules
31
+ - Any notable technical tradeoff or limitation
24
32
 
25
33
  ## Why
26
34
 
package/skills/review-fix-all/SKILL.md CHANGED
@@ -8,7 +8,7 @@ allowed-tools: Bash(bunx:*), Task
8
8
 
9
9
  1. Run the following command with a 1-hour timeout (RUN IT AS A BLOCKING, FOREGROUND TASK TO PREVENT PREMATURE TERMINATION): `bunx @willbooster/agent-skills@latest review --agent all`
10
10
  2. Merge the returned findings, deduplicating those that address the same underlying issue. If there are no findings, quit without modifying the code.
11
- 3. Accumulate every returned finding as a fact inside `## Verified Facts`, together with any returned `## Verified Facts` sections. Keep only facts that still affect review: what is known, why it matters, and how it was verified.
11
+ 3. Accumulate only review-meaningful facts inside `## Verified Facts`, together with any useful returned `## Verified Facts` sections. Keep facts that help avoid duplicate review work, such as current-code evidence, accepted constraints, or primary-source behavior; omit routine verification results and review-process history.
12
12
  4. Refine accumulated facts to reduce duplication and remove stale details, then pass them through stdin with heredoc syntax:
13
13
 
14
14
  ```bash
package/skills/review-fix-claude/SKILL.md CHANGED
@@ -8,7 +8,7 @@ allowed-tools: Bash(bunx:*)
8
8
 
9
9
  1. Run the following command with a 1-hour timeout (RUN IT AS A BLOCKING, FOREGROUND TASK TO PREVENT PREMATURE TERMINATION): `bunx @willbooster/agent-skills@latest review --agent claude`
10
10
  2. If the command returns `There is no concern.`, quit without modifying code. Otherwise, process the returned findings.
11
- 3. Accumulate every returned finding as a fact inside `## Verified Facts`, together with any returned `## Verified Facts`. Keep only facts that still affect review: what is known, why it matters, and how it was verified.
11
+ 3. Accumulate only review-meaningful facts inside `## Verified Facts`, together with any useful returned `## Verified Facts`. Keep facts that help avoid duplicate review work, such as current-code evidence, accepted constraints, or primary-source behavior; omit routine verification results and review-process history.
12
12
  4. Refine accumulated facts to reduce duplication and remove stale details, then pass them through stdin with heredoc syntax:
13
13
 
14
14
  ```bash
package/skills/review-fix-codex/SKILL.md CHANGED
@@ -8,7 +8,7 @@ allowed-tools: Bash(bunx:*)
8
8
 
9
9
  1. Run the following command with a 1-hour timeout (RUN IT AS A BLOCKING, FOREGROUND TASK TO PREVENT PREMATURE TERMINATION): `bunx @willbooster/agent-skills@latest review --agent codex`
10
10
  2. If the command returns `There is no concern.`, quit without modifying code. Otherwise, process the returned findings.
11
- 3. Accumulate every returned finding as a fact inside `## Verified Facts`, together with any returned `## Verified Facts`. Keep only facts that still affect review: what is known, why it matters, and how it was verified.
11
+ 3. Accumulate only review-meaningful facts inside `## Verified Facts`, together with any useful returned `## Verified Facts`. Keep facts that help avoid duplicate review work, such as current-code evidence, accepted constraints, or primary-source behavior; omit routine verification results and review-process history.
12
12
  4. Refine accumulated facts to reduce duplication and remove stale details, then pass them through stdin with heredoc syntax:
13
13
 
14
14
  ```bash
package/skills/review-fix-gemini/SKILL.md CHANGED
@@ -8,7 +8,7 @@ allowed-tools: Bash(bunx:*)
8
8
 
9
9
  1. Run the following command with a 1-hour timeout (RUN IT AS A BLOCKING, FOREGROUND TASK TO PREVENT PREMATURE TERMINATION): `bunx @willbooster/agent-skills@latest review --agent gemini`
10
10
  2. If the command returns `There is no concern.`, quit without modifying code. Otherwise, process the returned findings.
11
- 3. Accumulate every returned finding as a fact inside `## Verified Facts`, together with any returned `## Verified Facts`. Keep only facts that still affect review: what is known, why it matters, and how it was verified.
11
+ 3. Accumulate only review-meaningful facts inside `## Verified Facts`, together with any useful returned `## Verified Facts`. Keep facts that help avoid duplicate review work, such as current-code evidence, accepted constraints, or primary-source behavior; omit routine verification results and review-process history.
12
12
  4. Refine accumulated facts to reduce duplication and remove stale details, then pass them through stdin with heredoc syntax:
13
13
 
14
14
  ```bash
package/skills/update-pr/SKILL.md CHANGED
@@ -8,6 +8,9 @@ allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*)
8
8
 
9
9
  Commit and push any local changes to the current branch.
10
10
  Draft a new pull request title and body that accurately reflect the changes made against the base branch, keeping any existing issue-closing line, such as `Close #<issue>`, exactly once.
11
+ Include both customer-facing and technical summaries.
12
+ Write the customer-facing summary for non-technical readers who know nothing about the internal implementation and only need to understand specification, behavior, workflow, or user-visible impact.
13
+ Write the technical summary for engineers who want to understand code, architecture, dependencies, and implementation scope.
11
14
  Run the following command to update a pull request.
12
15
  Finally, report the pull request URL.
13
16
 
@@ -15,11 +18,17 @@ Finally, report the pull request URL.
15
18
  bunx @willbooster/agent-skills@latest update-pr "feat: concise PR title" <<'EOF'
16
19
  Close #<issue>
17
20
 
18
- ## Summary
21
+ ## Customer Summary
19
22
 
20
- - What changed
21
- - Key scope or affected area
22
- - Any notable tradeoff or limitation
23
+ - Specification, behavior, workflow, or user-visible changes
24
+ - Impact on customers, operators, or internal users
25
+ - Rollout, compatibility, or migration notes in non-technical language
26
+
27
+ ## Technical Summary
28
+
29
+ - Code, configuration, dependency, or architecture changes
30
+ - Key implementation scope or affected modules
31
+ - Any notable technical tradeoff or limitation
23
32
 
24
33
  ## Why
25
34
 
package/skills/wbfy/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: wbfy
3
- description: Apply `wbfy` to the current (target) repository.
3
+ description: Run `wbfy` command to the current (target) repository.
4
4
  allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*), Bash(yarn:*)
5
5
  ---
6
6