@willbooster/agent-skills 1.18.4 → 1.19.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.
package/README.md CHANGED
@@ -37,6 +37,7 @@ bunx skills@latest add WillBooster/agent-skills --agent claude-code --agent code
37
37
  | [`review-fix-all`](skills/review-fix-all/SKILL.md) / [`review-fix-claude`](skills/review-fix-claude/SKILL.md) / [`review-fix-codex`](skills/review-fix-codex/SKILL.md) / [`review-fix-gemini`](skills/review-fix-gemini/SKILL.md) | Yes | Review code and fix only still-valid findings. | `$review-fix-all` |
38
38
  | [`screenshot-claude`](skills/screenshot-claude/SKILL.md) / [`screenshot-codex`](skills/screenshot-codex/SKILL.md) / [`screenshot-gemini`](skills/screenshot-gemini/SKILL.md) | Yes | Take a page screenshot with a chosen agent. | `$screenshot-codex https://example.com "Pricing" "the comparison table"` |
39
39
  | [`simplify-pr-claude`](skills/simplify-pr-claude/SKILL.md) / [`simplify-pr-codex`](skills/simplify-pr-codex/SKILL.md) / [`simplify-pr-gemini`](skills/simplify-pr-gemini/SKILL.md) | Yes | Simplify the current PR with a chosen agent. | `$simplify-pr-codex` |
40
+ | [`stabilize-tests`](skills/stabilize-tests/SKILL.md) | No | Stabilize flaky or unreliable tests. | `$stabilize-tests test/auth.e2e.test.ts` |
40
41
  | [`update-pr`](skills/update-pr/SKILL.md) | No | Update the PR title and body. | `$complete-pr then $update-pr` |
41
42
  | [`wbfy`](skills/wbfy/SKILL.md) | No | Apply `wbfy` to the current repository. | `$wbfy` |
42
43
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@willbooster/agent-skills",
3
- "version": "1.18.4",
3
+ "version": "1.19.0",
4
4
  "description": "A collection of agent skills for WillBooster Inc.",
5
5
  "repository": {
6
6
  "type": "git",
@@ -4,8 +4,6 @@ description: Check the latest test-related CI results for the current pull reque
4
4
  allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*)
5
5
  ---
6
6
 
7
- # Check PR CI
8
-
9
7
  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 check-pr-ci`
10
8
 
11
9
  - Exit code `0`: all latest workflows succeeded.
@@ -0,0 +1,14 @@
1
+ ---
2
+ name: stabilize-tests
3
+ description: Stabilize flaky or unreliable tests by finding the root cause, fixing it, and rerunning the tests until they pass reliably.
4
+ ---
5
+
6
+ # Stabilize tests workflow
7
+
8
+ 1. Run the tests to identify unstable or flaky tests.
9
+ - If specific tests are specified, run only those tests; otherwise, run the entire test suite.
10
+ 2. Investigate the root cause of each unstable test before changing code.
11
+ 3. Implement fixes to stabilize the tests.
12
+ - Prefer actual API calls over mocks.
13
+ 4. Re-run the tests to confirm they pass reliably. If they fail, repeat steps 2-4 until they are stable.
14
+ 5. Commit and push the changes, then run either the `open-pr` or `update-pr` skill.
@@ -8,11 +8,11 @@ allowed-tools: Bash(bun:*), Bash(gh:*), Bash(git:*), Bash(yarn:*)
8
8
 
9
9
  1. If the current branch is `main`, create and switch to a new branch based on the latest remote `main` branch.
10
10
  - Ensure the new branch is derived from the latest remote `main` branch to prevent merge conflicts when opening a pull request (PR).
11
- 2. Run `yarn start <root_path_of_target_repo>` inside `~/ghq/github.com/WillBooster/wbfy`.
11
+ 2. Run `yarn start <root_path_of_target_repo>` inside `~/ghq/github.com/WillBooster/shared/packages/wbfy`.
12
12
  3. Run either `yarn check-for-ai` or `bun check-for-ai` in the target repository (do not run this within the `wbfy` directory).
13
13
  4. If any checks fail, resolve them using one of the following methods:
14
14
  - If the failure originates in the target repository (e.g., existing code violates new linter rules), fix the issue there, commit and push the changes, then return to step 3.
15
- - If the failure is caused by configuration files modified by `wbfy` (e.g., a `wbfy`-edited `tsconfig.json` does not match the target repository), fix the issue in `~/ghq/github.com/WillBooster/wbfy`, commit and push the changes, open a PR in the `wbfy` repository, then return to step 2.
15
+ - If the failure is caused by configuration files modified by `wbfy` (e.g., a `wbfy`-edited `tsconfig.json` does not match the target repository), fix the issue in the `wbfy` directory, commit and push the changes, open a PR in the `wbfy` repository, then return to step 2.
16
16
  - Ensure `wbfy` generates the correct configuration files without manual adjustments, as all projects rely on its automation.
17
17
  - Avoid ad-hoc hotfixes; prefer general and versatile solutions applicable to all projects.
18
18
  - Add comments to the `wbfy` codebase to clarify the reasoning behind your fixes.