@willbooster/agent-skills 1.21.2 → 1.21.4

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 (2) hide show
  1. package/package.json +1 -1
  2. package/skills/complete-pr/SKILL.md +5 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@willbooster/agent-skills",
3
- "version": "1.21.2",
3
+ "version": "1.21.4",
4
4
  "description": "A collection of agent skills for WillBooster Inc.",
5
5
  "repository": {
6
6
  "type": "git",
package/skills/complete-pr/SKILL.md CHANGED
@@ -3,10 +3,10 @@ name: complete-pr
3
3
  description: Complete GitHub pull requests by iterating on CI and review feedback until the PR is ready.
4
4
  ---
5
5
 
6
- Read the PR body and its messages using the `fetch-pr` skill.
7
- Then, merge the latest remote `main` branch into the current branch fixing any conflicts and push it.
8
- After that, fetch the current repository owner with `gh repo view --json owner --jq '.owner.login'`.
9
- If the owner is `WillBooster` or `WillBoosterLab`, follow the first workflow below. Otherwise, follow the second workflow below.
6
+ Use the `fetch-pr` skill to read the PR body and its messages.
7
+ Fetch the latest changes from the remote. If the remote default branch has new commits, merge it into the current branch, resolve any conflicts, and push the changes.
8
+ Next, fetch the current repository owner using the command `gh repo view --json owner --jq '.owner.login'`.
9
+ If the owner is `WillBooster` or `WillBoosterLab`, follow the first workflow below; otherwise, follow the second workflow.
10
10
 
11
11
  ## Workflow for `WillBooster` or `WillBoosterLab` repositories
12
12
 
@@ -17,7 +17,7 @@ If the owner is `WillBooster` or `WillBoosterLab`, follow the first workflow bel
17
17
  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.
18
18
  - If there are valid review comments that are out of scope for the current PR, create new issues for them.
19
19
  6. Reply to all review threads using the `manage-pr-review-threads` skill.
20
- 7. If you made changes in step 5, commit and push them, post `/gemini review` on the PR, wait for 3 minutes (`sleep 3m`), and return to step 1.
20
+ 7. If you made changes in step 5, commit and push them, post `/gemini review` on the PR, wait for 5 minutes (`sleep 5m`), and return to step 1.
21
21
  8. Update the PR title and body using the `update-pr` skill to reflect all changes.
22
22
 
23
23
  ## Workflow for the other repositories