@willbooster/agent-skills 1.16.0 → 1.17.0

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 (40) hide show
  1. package/README.md +6 -0
  2. package/dist/cli.js +3 -3
  3. package/package.json +3 -2
  4. package/skills/check-pr-ci/SKILL.md +12 -0
  5. package/skills/complete-pr/SKILL.md +32 -0
  6. package/skills/fetch-issue/SKILL.md +9 -0
  7. package/skills/fetch-pr/SKILL.md +9 -0
  8. package/skills/fix-bug/SKILL.md +21 -0
  9. package/skills/manage-pr-review-threads/SKILL.md +35 -0
  10. package/skills/open-pr/SKILL.md +39 -0
  11. package/skills/plan-issue-claude/SKILL.md +10 -0
  12. package/skills/plan-issue-codex/SKILL.md +10 -0
  13. package/skills/plan-issue-gemini/SKILL.md +10 -0
  14. package/skills/playwright-cli/SKILL.md +331 -0
  15. package/skills/playwright-cli/references/element-attributes.md +23 -0
  16. package/skills/playwright-cli/references/playwright-tests.md +39 -0
  17. package/skills/playwright-cli/references/request-mocking.md +87 -0
  18. package/skills/playwright-cli/references/running-code.md +231 -0
  19. package/skills/playwright-cli/references/session-management.md +170 -0
  20. package/skills/playwright-cli/references/storage-state.md +275 -0
  21. package/skills/playwright-cli/references/test-generation.md +88 -0
  22. package/skills/playwright-cli/references/tracing.md +142 -0
  23. package/skills/playwright-cli/references/video-recording.md +146 -0
  24. package/skills/refactor-structure/SKILL.md +12 -0
  25. package/skills/review-all/SKILL.md +13 -0
  26. package/skills/review-claude/SKILL.md +10 -0
  27. package/skills/review-codex/SKILL.md +10 -0
  28. package/skills/review-fix-all/SKILL.md +17 -0
  29. package/skills/review-fix-claude/SKILL.md +15 -0
  30. package/skills/review-fix-codex/SKILL.md +15 -0
  31. package/skills/review-fix-gemini/SKILL.md +15 -0
  32. package/skills/review-gemini/SKILL.md +10 -0
  33. package/skills/screenshot-claude/SKILL.md +13 -0
  34. package/skills/screenshot-codex/SKILL.md +13 -0
  35. package/skills/screenshot-gemini/SKILL.md +13 -0
  36. package/skills/simplify-pr-claude/SKILL.md +10 -0
  37. package/skills/simplify-pr-codex/SKILL.md +10 -0
  38. package/skills/simplify-pr-gemini/SKILL.md +10 -0
  39. package/skills/update-pr/SKILL.md +60 -0
  40. package/skills/wbfy/SKILL.md +17 -0
@@ -0,0 +1,17 @@
1
+ ---
2
+ name: review-fix-all
3
+ description: Run Codex, Claude Code, and Gemini CLI reviews against the current branch concurrently, deduplicate the findings, and fix only the review comments that are still valid for the current codebase.
4
+ allowed-tools: Bash(bunx:*), Task
5
+ ---
6
+
7
+ # Review workflow
8
+
9
+ 1. Run the following command with a 1-hour timeout (DO NOT STOP THE COMMAND BEFORE 1 HOUR ELAPSES): `bunx @willbooster/agent-skills@latest review --agent all`
10
+ 2. Treat the combined output as candidate comments generated by multiple agents running concurrently.
11
+ 3. Merge the review results into a single set of candidate comments, deduplicating those that address the same underlying issue.
12
+ 4. If there are no candidate comments, quit the workflow without modifying the code.
13
+ 5. Determine whether each candidate comment is still valid for the current codebase.
14
+ 6. Address valid review comments by updating the code. For invalid comments, add explanatory comments to the code detailing why the existing implementation is necessary.
15
+ - If there are valid review comments that are out of scope for the current PR, create new issues for them.
16
+ 7. If you made any code changes, commit and push them to the current branch.
17
+ 8. If you fixed any valid comments, return to step 1. Otherwise, quit the workflow.
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: review-fix-claude
3
+ description: Run Claude Code review against the current branch, fix only the review comments that are still valid for the current codebase, and leave invalid comments unchanged.
4
+ allowed-tools: Bash(bunx:*)
5
+ ---
6
+
7
+ # Review workflow
8
+
9
+ 1. Run the following command with a 1-hour timeout (DO NOT STOP THE COMMAND BEFORE 1 HOUR ELAPSES): `bunx @willbooster/agent-skills@latest review --agent claude`
10
+ 2. Treat the returned review results as the candidate comment set to process. If the command returns `There is no concern.`, quit without modifying code.
11
+ 3. Determine whether each candidate comment is still valid for the current codebase.
12
+ 4. Address valid review comments by updating the code. For invalid comments, add explanatory comments to the code detailing why the existing implementation is necessary.
13
+ - If there are valid review comments that are out of scope for the current PR, create new issues for them.
14
+ 5. If you made any code changes, commit and push them to the current branch.
15
+ 6. If you fixed any valid comments, return to step 1. Otherwise, quit the workflow.
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: review-fix-codex
3
+ description: Run Codex code review against the current branch, fix only the review comments that are still valid for the current codebase, and leave invalid comments unchanged.
4
+ allowed-tools: Bash(bunx:*)
5
+ ---
6
+
7
+ # Review workflow
8
+
9
+ 1. Run the following command with a 1-hour timeout (DO NOT STOP THE COMMAND BEFORE 1 HOUR ELAPSES): `bunx @willbooster/agent-skills@latest review --agent codex`
10
+ 2. Treat the returned review results as the candidate comment set to process. If the command returns `There is no concern.`, quit without modifying code.
11
+ 3. Determine whether each candidate comment is still valid for the current codebase.
12
+ 4. Address valid review comments by updating the code. For invalid comments, add explanatory comments to the code detailing why the existing implementation is necessary.
13
+ - If there are valid review comments that are out of scope for the current PR, create new issues for them.
14
+ 5. If you made any code changes, commit and push them to the current branch.
15
+ 6. If you fixed any valid comments, return to step 1. Otherwise, quit the workflow.
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: review-fix-gemini
3
+ description: Run Gemini CLI review against the current branch, fix only the review comments that are still valid for the current codebase, and leave invalid comments unchanged.
4
+ allowed-tools: Bash(bunx:*)
5
+ ---
6
+
7
+ # Review workflow
8
+
9
+ 1. Run the following command with a 1-hour timeout (DO NOT STOP THE COMMAND BEFORE 1 HOUR ELAPSES): `bunx @willbooster/agent-skills@latest review --agent gemini`
10
+ 2. Treat the returned review results as the candidate comment set to process. If the command returns `There is no concern.`, quit without modifying code.
11
+ 3. Determine whether each candidate comment is still valid for the current codebase.
12
+ 4. Address valid review comments by updating the code. For invalid comments, add explanatory comments to the code detailing why the existing implementation is necessary.
13
+ - If there are valid review comments that are out of scope for the current PR, create new issues for them.
14
+ 5. If you made any code changes, commit and push them to the current branch.
15
+ 6. If you fixed any valid comments, return to step 1. Otherwise, quit the workflow.
@@ -0,0 +1,10 @@
1
+ ---
2
+ name: review-gemini
3
+ description: Run Gemini CLI review against the current branch and report only the review comments that are still valid for the current codebase, without applying fixes.
4
+ allowed-tools: Bash(bunx:*)
5
+ ---
6
+
7
+ # Review workflow
8
+
9
+ 1. Run the following command with a 1-hour timeout (DO NOT STOP THE COMMAND BEFORE 1 HOUR ELAPSES): `bunx @willbooster/agent-skills@latest review --agent gemini`
10
+ 2. Report on the review results.
@@ -0,0 +1,13 @@
1
+ ---
2
+ name: screenshot-claude
3
+ description: Run Claude Code to take a screenshot for a specific page.
4
+ allowed-tools: Bash(bunx:*)
5
+ ---
6
+
7
+ # Screenshot workflow
8
+
9
+ 1. Run the following command with a 1-hour timeout (DO NOT STOP THE COMMAND BEFORE 1 HOUR ELAPSES): `bunx @willbooster/agent-skills@latest screenshot --agent claude <initial-url> <page-name> <description>`
10
+ - `<initial-url>`: Initial URL to open before navigating
11
+ - `<page-name>`: Page name to navigate to from the initial page
12
+ - `<description>`: Description of the part to capture in the screenshot
13
+ 2. Report the screenshot file path returned by the agent.
@@ -0,0 +1,13 @@
1
+ ---
2
+ name: screenshot-codex
3
+ description: Run Codex to take a screenshot for a specific page.
4
+ allowed-tools: Bash(bunx:*)
5
+ ---
6
+
7
+ # Screenshot workflow
8
+
9
+ 1. Run the following command with a 1-hour timeout (DO NOT STOP THE COMMAND BEFORE 1 HOUR ELAPSES): `bunx @willbooster/agent-skills@latest screenshot --agent codex <initial-url> <page-name> <description>`
10
+ - `<initial-url>`: Initial URL to open before navigating
11
+ - `<page-name>`: Page name to navigate to from the initial page
12
+ - `<description>`: Description of the part to capture in the screenshot
13
+ 2. Report the screenshot file path returned by the agent.
@@ -0,0 +1,13 @@
1
+ ---
2
+ name: screenshot-gemini
3
+ description: Run Gemini CLI to take a screenshot for a specific page.
4
+ allowed-tools: Bash(bunx:*)
5
+ ---
6
+
7
+ # Screenshot workflow
8
+
9
+ 1. Run the following command with a 1-hour timeout (DO NOT STOP THE COMMAND BEFORE 1 HOUR ELAPSES): `bunx @willbooster/agent-skills@latest screenshot --agent gemini <initial-url> <page-name> <description>`
10
+ - `<initial-url>`: Initial URL to open before navigating
11
+ - `<page-name>`: Page name to navigate to from the initial page
12
+ - `<description>`: Description of the part to capture in the screenshot
13
+ 2. Report the screenshot file path returned by the agent.
@@ -0,0 +1,10 @@
1
+ ---
2
+ name: simplify-pr-claude
3
+ description: Use Claude Code to simplify the current pull request by safely reducing unnecessary scope, complexity, and noise while preserving the intended outcome.
4
+ allowed-tools: Bash(bunx:*)
5
+ ---
6
+
7
+ # PR simplification workflow
8
+
9
+ 1. Run the following command with a 1-hour timeout (DO NOT STOP THE COMMAND BEFORE 1 HOUR ELAPSES): `bunx @willbooster/agent-skills@latest simplify --agent claude`
10
+ 2. Report on the simplification results.
@@ -0,0 +1,10 @@
1
+ ---
2
+ name: simplify-pr-codex
3
+ description: Use Codex to simplify the current pull request by safely reducing unnecessary scope, complexity, and noise while preserving the intended outcome.
4
+ allowed-tools: Bash(bunx:*)
5
+ ---
6
+
7
+ # PR simplification workflow
8
+
9
+ 1. Run the following command with a 1-hour timeout (DO NOT STOP THE COMMAND BEFORE 1 HOUR ELAPSES): `bunx @willbooster/agent-skills@latest simplify --agent codex`
10
+ 2. Report on the simplification results.
@@ -0,0 +1,10 @@
1
+ ---
2
+ name: simplify-pr-gemini
3
+ description: Use Gemini CLI to simplify the current pull request by safely reducing unnecessary scope, complexity, and noise while preserving the intended outcome.
4
+ allowed-tools: Bash(bunx:*)
5
+ ---
6
+
7
+ # PR simplification workflow
8
+
9
+ 1. Run the following command with a 1-hour timeout (DO NOT STOP THE COMMAND BEFORE 1 HOUR ELAPSES): `bunx @willbooster/agent-skills@latest simplify --agent gemini`
10
+ 2. Report on the simplification results.
@@ -0,0 +1,60 @@
1
+ ---
2
+ name: update-pr
3
+ description: Update the pull request title and body for the current branch in the current repository.
4
+ allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*)
5
+ ---
6
+
7
+ # Update PR workflow
8
+
9
+ Write the full replacement pull request title and the complete replacement PR body so they reflect the current scope, motivation, and validation.
10
+ Run `update-pr-title` first, then run `update-pr-body`.
11
+ Finally, report the pull request URL.
12
+
13
+ ## Update the PR title
14
+
15
+ ```bash
16
+ bunx @willbooster/agent-skills@latest update-pr-title <<'EOF'
17
+ feat: concise PR title
18
+ EOF
19
+ ```
20
+
21
+ Note that the prefix of the PR title must follow the Conventional Commits specification:
22
+
23
+ - feat: A new feature for the user or API.
24
+ - fix: A bug fix for the user or API.
25
+ - build: Changes that affect the build system or external dependencies (e.g., npm, webpack, typescript).
26
+ - chore: Routine tasks, maintenance, or tooling changes that don't modify source or test files.
27
+ - ci: Changes to CI/CD configuration files and scripts.
28
+ - docs: Documentation-only changes.
29
+ - perf: A code change that improves performance.
30
+ - refactor: A code change that neither fixes a bug nor adds a feature, but improves code structure or readability.
31
+ - style: Changes that do not affect the meaning of the code (e.g., formatting).
32
+ - test: Adding missing tests or correcting existing tests.
33
+
34
+ ## Update the PR body
35
+
36
+ ```bash
37
+ bunx @willbooster/agent-skills@latest update-pr-body <<'EOF'
38
+ Close #<issue>
39
+
40
+ ## Summary
41
+
42
+ - What changed
43
+ - Key scope or affected area
44
+ - Any notable tradeoff or limitation
45
+
46
+ ## Why
47
+
48
+ - Problem being solved
49
+ - Reason this approach was chosen
50
+
51
+ ## Testing
52
+
53
+ - Exact commands run
54
+ - Manual verification steps if relevant
55
+
56
+ ## Notes (if needed)
57
+
58
+ - Breaking changes, rollout concerns, screenshots, or follow-up work
59
+ EOF
60
+ ```
@@ -0,0 +1,17 @@
1
+ ---
2
+ name: wbfy
3
+ description: Apply `wbfy` to the current repository.
4
+ allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*), Bash(yarn:*)
5
+ ---
6
+
7
+ # wbfy application workflow
8
+
9
+ 1. If the current branch is `main`, create and switch to a new branch from the latest remote `main` branch.
10
+ - Make sure the branch is derived from the latest remote `main` branch to avoid merge conflicts when opening a PR.
11
+ 2. Run `yarn start <directory_path_of_target_repo>` in `~/ghq/github.com/WillBooster/wbfy`.
12
+ 3. Run `yarn check-for-ai` or `bun check-for-ai` in the target repository (do not run this in `wbfy`).
13
+ 4. If any checks fail, do one of the following:
14
+ - Fix the issues in the target repository, then return to step 2.
15
+ - If the failure originates from `wbfy`, fix `~/ghq/github.com/WillBooster/wbfy`, commit and push the changes, open a PR in the `wbfy` repository, then return to step 1.
16
+ 5. Commit and push any changes in the target repository, then open a PR.
17
+ - `wbfy` creates, modifies, and deletes many files in the target repository, so be sure to include all of them in the commit.