@willbooster/agent-skills 1.28.6 → 1.28.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@willbooster/agent-skills",
-  "version": "1.28.6",
+  "version": "1.28.7",
   "description": "A collection of agent skills for WillBooster Inc.",
   "repository": {
     "type": "git",

package/skills/open-pr/SKILL.md

@@ -8,7 +8,9 @@ allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*)
 
 Commit and push any local changes to the current branch.
 Write a PR body that helps reviewers quickly understand the scope, motivation, and validation.
-Include the linked issue when applicable, a concise summary of the changes, the reasoning behind them, and how they were tested.
+Include the linked issue when applicable, both customer-facing and technical summaries, the reasoning behind the changes, and how they were tested.
+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.
+Write the technical summary for engineers who want to understand code, architecture, dependencies, and implementation scope.
 Run the following command to open a pull request.
 Finally, report the PR URL.
 
@@ -16,11 +18,17 @@ Finally, report the PR URL.
 bunx @willbooster/agent-skills@latest open-pr "feat: concise PR title" <<'EOF'
 Close #<issue>
 
-## Summary
+## Customer Summary
 
-- What changed
-- Key scope or affected area
-- Any notable tradeoff or limitation
+- Specification, behavior, workflow, or user-visible changes
+- Impact on customers, operators, or internal users
+- Rollout, compatibility, or migration notes in non-technical language
+
+## Technical Summary
+
+- Code, configuration, dependency, or architecture changes
+- Key implementation scope or affected modules
+- Any notable technical tradeoff or limitation
 
 ## Why
 

package/skills/update-pr/SKILL.md

@@ -8,6 +8,9 @@ allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*)
 
 Commit and push any local changes to the current branch.
 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.
+Include both customer-facing and technical summaries.
+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.
+Write the technical summary for engineers who want to understand code, architecture, dependencies, and implementation scope.
 Run the following command to update a pull request.
 Finally, report the pull request URL.
 
@@ -15,11 +18,17 @@ Finally, report the pull request URL.
 bunx @willbooster/agent-skills@latest update-pr "feat: concise PR title" <<'EOF'
 Close #<issue>
 
-## Summary
+## Customer Summary
 
-- What changed
-- Key scope or affected area
-- Any notable tradeoff or limitation
+- Specification, behavior, workflow, or user-visible changes
+- Impact on customers, operators, or internal users
+- Rollout, compatibility, or migration notes in non-technical language
+
+## Technical Summary
+
+- Code, configuration, dependency, or architecture changes
+- Key implementation scope or affected modules
+- Any notable technical tradeoff or limitation
 
 ## Why
 

package/skills/wbfy/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wbfy
-description: Apply `wbfy` to the current (target) repository.
+description: Run `wbfy` command to the current (target) repository.
 allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*), Bash(yarn:*)
 ---