Skip to content

Commit 31adca1

Browse files
WillBooster-botWillBooster-bot
committed
chore: willboosterify this repo
1 parent 9f47e8b commit 31adca1

File tree

14 files changed

+522
-396
lines changed

14 files changed

+522
-396
lines changed

‎.cursor/rules/general.mdc‎

Lines changed: 22 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -10,16 +10,29 @@ alwaysApply: true
1010
- Description: undefined
1111
- Package Manager: yarn
1212

13-
## General Instructions
13+
## Development Workflow
1414

15-
- Do not write tests unless explicitly requested.
16-
- When fixing tests, gather debug information through logging and screenshots before modifying the code.
17-
- After making code changes, run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only.
18-
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
19-
- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
20-
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
21-
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Cursor) <agent@willbooster.com>`.
22-
- Always create new commits. Avoid using `--amend`.
15+
When changing code, complete these steps before responding to the user.
16+
17+
1. If the current branch is `main`, create a new branch.
18+
- Include unexpected changes since they are mine.
19+
2. Make code changes as needed.
20+
3. If possible, write e2e tests for your changes.
21+
4. Run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only.
22+
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
23+
5. Commit your changes to the current branch and push.
24+
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, `test:`, etc.
25+
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Cursor) <agent@willbooster.com>`.
26+
- When pre-commit hooks prevent your changes, fix your code, then re-commit and re-push.
27+
6. Create a pull request using `gh`.
28+
- The pull request title should match your commit message.
29+
7. Repeat the following steps until the test workflow passes:
30+
1. Wait and check the CI results using `sleep 5m` and `gh` until the test workflow completes.
31+
2. If tests fail, identify the root causes by gathering debug information through logging and screenshots, then fix the code and/or tests.
32+
3. Fetch unresolved review comments from the pull request using `gh` and address them.
33+
- e.g., `gh api graphql -f query='{ repository(owner: "WillBooster", name: "shared") { pullRequest(number: 24) { reviewThreads(first: 100) { nodes { isResolved comments(first: 100) { nodes { body author { login } path line } } } } } } }' | jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved == false)'`
34+
4. Commit your changes and push.
35+
5. Write `/gemini review` in the pull request.
2336

2437
## Coding Style
2538

‎.github/workflows/autofix.yml‎

Lines changed: 3 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,9 @@
1-
name: autofix.ci
1+
name: Fix code automatically
22
on:
33
pull_request:
4-
push:
5-
branches:
6-
- main
7-
permissions:
8-
contents: read
94
concurrency:
10-
group: autofix-${{ github.head_ref }}
5+
group: ${{ github.workflow }}-${{ github.ref }}
116
cancel-in-progress: true
127
jobs:
138
autofix:
14-
runs-on: ubuntu-latest
15-
steps:
16-
- uses: actions/checkout@v6
17-
- uses: actions/setup-node@v6
18-
with:
19-
check-latest: true
20-
- run: yarn install
21-
- run: yarn run cleanup
22-
- run: yarn run build
23-
- uses: autofix-ci/action@v1
9+
uses: WillBooster/reusable-workflows/.github/workflows/autofix.yml@main

‎.github/workflows/release.yml‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@ concurrency:
77
group: ${{ github.workflow }}
88
cancel-in-progress: false
99
permissions:
10-
id-token: write
1110
contents: write
1211
jobs:
1312
release:

‎AGENTS.md‎

Lines changed: 22 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,29 @@
44
- Description: undefined
55
- Package Manager: yarn
66

7-
## General Instructions
7+
## Development Workflow
88

9-
- Do not write tests unless explicitly requested.
10-
- When fixing tests, gather debug information through logging and screenshots before modifying the code.
11-
- After making code changes, run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only.
12-
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
13-
- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
14-
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
15-
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>`.
16-
- Always create new commits. Avoid using `--amend`.
9+
When changing code, complete these steps before responding to the user.
10+
11+
1. If the current branch is `main`, create a new branch.
12+
- Include unexpected changes since they are mine.
13+
2. Make code changes as needed.
14+
3. If possible, write e2e tests for your changes.
15+
4. Run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only.
16+
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
17+
5. Commit your changes to the current branch and push.
18+
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, `test:`, etc.
19+
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>`.
20+
- When pre-commit hooks prevent your changes, fix your code, then re-commit and re-push.
21+
6. Create a pull request using `gh`.
22+
- The pull request title should match your commit message.
23+
7. Repeat the following steps until the test workflow passes:
24+
1. Wait and check the CI results using `sleep 5m` and `gh` until the test workflow completes.
25+
2. If tests fail, identify the root causes by gathering debug information through logging and screenshots, then fix the code and/or tests.
26+
3. Fetch unresolved review comments from the pull request using `gh` and address them.
27+
- e.g., `gh api graphql -f query='{ repository(owner: "WillBooster", name: "shared") { pullRequest(number: 24) { reviewThreads(first: 100) { nodes { isResolved comments(first: 100) { nodes { body author { login } path line } } } } } } }' | jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved == false)'`
28+
4. Commit your changes and push.
29+
5. Write `/gemini review` in the pull request.
1730

1831
## Coding Style
1932

‎CLAUDE.md‎

Lines changed: 22 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,29 @@
44
- Description: undefined
55
- Package Manager: yarn
66

7-
## General Instructions
7+
## Development Workflow
88

9-
- Do not write tests unless explicitly requested.
10-
- When fixing tests, gather debug information through logging and screenshots before modifying the code.
11-
- After making code changes, run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only.
12-
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
13-
- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
14-
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
15-
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>`.
16-
- Always create new commits. Avoid using `--amend`.
9+
When changing code, complete these steps before responding to the user.
10+
11+
1. If the current branch is `main`, create a new branch.
12+
- Include unexpected changes since they are mine.
13+
2. Make code changes as needed.
14+
3. If possible, write e2e tests for your changes.
15+
4. Run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only.
16+
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
17+
5. Commit your changes to the current branch and push.
18+
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, `test:`, etc.
19+
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>`.
20+
- When pre-commit hooks prevent your changes, fix your code, then re-commit and re-push.
21+
6. Create a pull request using `gh`.
22+
- The pull request title should match your commit message.
23+
7. Repeat the following steps until the test workflow passes:
24+
1. Wait and check the CI results using `sleep 5m` and `gh` until the test workflow completes.
25+
2. If tests fail, identify the root causes by gathering debug information through logging and screenshots, then fix the code and/or tests.
26+
3. Fetch unresolved review comments from the pull request using `gh` and address them.
27+
- e.g., `gh api graphql -f query='{ repository(owner: "WillBooster", name: "shared") { pullRequest(number: 24) { reviewThreads(first: 100) { nodes { isResolved comments(first: 100) { nodes { body author { login } path line } } } } } } }' | jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved == false)'`
28+
4. Commit your changes and push.
29+
5. Write `/gemini review` in the pull request.
1730

1831
## Coding Style
1932

‎GEMINI.md‎

Lines changed: 22 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,29 @@
44
- Description: undefined
55
- Package Manager: yarn
66

7-
## General Instructions
7+
## Development Workflow
88

9-
- Do not write tests unless explicitly requested.
10-
- When fixing tests, gather debug information through logging and screenshots before modifying the code.
11-
- After making code changes, run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only.
12-
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
13-
- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
14-
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
15-
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Gemini CLI) <agent@willbooster.com>`.
16-
- Always create new commits. Avoid using `--amend`.
9+
When changing code, complete these steps before responding to the user.
10+
11+
1. If the current branch is `main`, create a new branch.
12+
- Include unexpected changes since they are mine.
13+
2. Make code changes as needed.
14+
3. If possible, write e2e tests for your changes.
15+
4. Run `yarn check-all-for-ai` to execute all tests (note: this may take up to 30 minutes), or run `yarn check-for-ai` for type checking and linting only.
16+
- If you are confident your changes will not break any tests, you may use `check-for-ai`.
17+
5. Commit your changes to the current branch and push.
18+
- Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, `test:`, etc.
19+
- Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Gemini CLI) <agent@willbooster.com>`.
20+
- When pre-commit hooks prevent your changes, fix your code, then re-commit and re-push.
21+
6. Create a pull request using `gh`.
22+
- The pull request title should match your commit message.
23+
7. Repeat the following steps until the test workflow passes:
24+
1. Wait and check the CI results using `sleep 5m` and `gh` until the test workflow completes.
25+
2. If tests fail, identify the root causes by gathering debug information through logging and screenshots, then fix the code and/or tests.
26+
3. Fetch unresolved review comments from the pull request using `gh` and address them.
27+
- e.g., `gh api graphql -f query='{ repository(owner: "WillBooster", name: "shared") { pullRequest(number: 24) { reviewThreads(first: 100) { nodes { isResolved comments(first: 100) { nodes { body author { login } path line } } } } } } }' | jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved == false)'`
28+
4. Commit your changes and push.
29+
5. Write `/gemini review` in the pull request.
1730

1831
## Coding Style
1932

‎package.json‎

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,14 +11,12 @@
1111
"scripts": {
1212
"build": "yarn workspaces foreach --all --parallel --verbose run build",
1313
"check-all-for-ai": "yarn check-for-ai && yarn test",
14-
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn lint-fix --quiet && yarn typecheck",
14+
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn typecheck && yarn lint-fix --quiet",
1515
"cleanup": "yarn format && yarn lint-fix",
1616
"format": "sort-package-json && yarn prettify && yarn workspaces foreach --all --parallel --verbose run format",
1717
"postinstall": "husky || true",
1818
"lint": "yarn workspaces foreach --all --parallel --verbose run lint",
1919
"lint-fix": "yarn workspaces foreach --all --parallel --verbose run lint-fix",
20-
"prepack": "pinst --disable",
21-
"postpack": "pinst --enable",
2220
"prepare": "husky || true",
2321
"prettify": "prettier --cache --color --write \"**/{.*/,}*.{cjs,css,cts,htm,html,java,js,json,json5,jsonc,jsx,md,mjs,mts,scss,ts,tsx,vue,yaml,yml}\" \"!**/packages/**\" \"!**/test{-,/}fixtures/**\" || true",
2422
"release": "yarn multi-semantic-release --debug",
@@ -34,15 +32,14 @@
3432
"@types/eslint": "9.6.1",
3533
"@willbooster/prettier-config": "10.2.4",
3634
"conventional-changelog-conventionalcommits": "9.1.0",
37-
"eslint": "9.39.1",
35+
"eslint": "9.39.2",
3836
"husky": "9.1.7",
3937
"lint-staged": "16.2.7",
4038
"micromatch": "4.0.8",
41-
"pinst": "3.0.0",
4239
"prettier": "3.7.4",
4340
"prettier-plugin-java": "2.7.7",
4441
"semantic-release": "25.0.2",
45-
"sort-package-json": "3.6.0",
42+
"sort-package-json": "3.5.0",
4643
"typescript": "5.9.3"
4744
},
4845
"packageManager": "yarn@4.12.0",

‎packages/shared-lib-blitz-next/package.json‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@
3333
"scripts": {
3434
"build": "build-ts lib",
3535
"check-all-for-ai": "yarn check-for-ai && yarn test",
36-
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn lint-fix --quiet && yarn typecheck",
36+
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn typecheck && yarn lint-fix --quiet",
3737
"cleanup": "yarn format && yarn lint-fix",
3838
"format": "sort-package-json && yarn prettify",
3939
"lint": "eslint --color",
@@ -50,7 +50,7 @@
5050
"@willbooster/prettier-config": "10.2.4",
5151
"blitz": "3.0.2",
5252
"build-ts": "17.0.9",
53-
"eslint": "9.39.1",
53+
"eslint": "9.39.2",
5454
"eslint-config-flat-gitignore": "2.1.0",
5555
"eslint-config-prettier": "10.1.8",
5656
"eslint-import-resolver-typescript": "4.4.4",
@@ -64,7 +64,7 @@
6464
"micromatch": "4.0.8",
6565
"prettier": "3.7.4",
6666
"prettier-plugin-java": "2.7.7",
67-
"sort-package-json": "3.6.0",
67+
"sort-package-json": "3.5.0",
6868
"typescript": "5.9.3",
6969
"typescript-eslint": "8.50.0",
7070
"vitest": "4.0.15"

‎packages/shared-lib-next/package.json‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@
3333
"scripts": {
3434
"build": "build-ts lib",
3535
"check-all-for-ai": "yarn check-for-ai && yarn test",
36-
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn lint-fix --quiet && yarn typecheck",
36+
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn typecheck && yarn lint-fix --quiet",
3737
"cleanup": "yarn format && yarn lint-fix",
3838
"format": "sort-package-json && yarn prettify",
3939
"lint": "eslint --color",
@@ -49,7 +49,7 @@
4949
"@willbooster/eslint-config-ts": "11.4.12",
5050
"@willbooster/prettier-config": "10.2.4",
5151
"build-ts": "17.0.9",
52-
"eslint": "9.39.1",
52+
"eslint": "9.39.2",
5353
"eslint-config-flat-gitignore": "2.1.0",
5454
"eslint-config-prettier": "10.1.8",
5555
"eslint-import-resolver-typescript": "4.4.4",
@@ -64,7 +64,7 @@
6464
"next": "16.1.0",
6565
"prettier": "3.7.4",
6666
"prettier-plugin-java": "2.7.7",
67-
"sort-package-json": "3.6.0",
67+
"sort-package-json": "3.5.0",
6868
"typescript": "5.9.3",
6969
"typescript-eslint": "8.50.0",
7070
"vitest": "4.0.15"

‎packages/shared-lib-node/package.json‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@
3333
"scripts": {
3434
"build": "build-ts lib",
3535
"check-all-for-ai": "yarn check-for-ai && yarn test",
36-
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn lint-fix --quiet && yarn typecheck",
36+
"check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn typecheck && yarn lint-fix --quiet",
3737
"cleanup": "yarn format && yarn lint-fix",
3838
"format": "sort-package-json && yarn prettify",
3939
"lint": "eslint --color",
@@ -56,7 +56,7 @@
5656
"@willbooster/eslint-config-ts": "11.4.12",
5757
"@willbooster/prettier-config": "10.2.4",
5858
"build-ts": "17.0.9",
59-
"eslint": "9.39.1",
59+
"eslint": "9.39.2",
6060
"eslint-config-flat-gitignore": "2.1.0",
6161
"eslint-config-prettier": "10.1.8",
6262
"eslint-import-resolver-typescript": "4.4.4",
@@ -70,7 +70,7 @@
7070
"micromatch": "4.0.8",
7171
"prettier": "3.7.4",
7272
"prettier-plugin-java": "2.7.7",
73-
"sort-package-json": "3.6.0",
73+
"sort-package-json": "3.5.0",
7474
"typescript": "5.9.3",
7575
"typescript-eslint": "8.50.0",
7676
"vitest": "4.0.15"

0 commit comments

Comments
 (0)