chore: willboosterify this repo

WillBooster-bot · WillBooster-bot · commit dbcb7043ab27 · 2026-02-10T02:14:37.000+09:00
diff --git a/.cursor/rules/general.mdc b/.cursor/rules/general.mdc
@@ -8,23 +8,26 @@ alwaysApply: true
 
 - Name: @exercode/problem-utils
 - Description: :100: A set of utilities for judging programs on Exercode (https://exercode.willbooster.com/).
-- Package Manager: yarn
+- Package Manager: yarn on zsh
 
 ## General Instructions
 
+- Create a new branch if the current branch is `main`.
 - Do not write tests unless explicitly requested.
 - When fixing tests, gather debug information through logging and screenshots before modifying the code.
-- 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.
+- After making code changes, run `yarn check-all-for-ai` to execute all tests (takes up to 1 hour), or run `yarn check-for-ai` for type checking and linting only (takes up to 10 minutes).
   - If you are confident your changes will not break any tests, you may use `check-for-ai`.
-- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
-  - Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
-  - Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Cursor) <agent@willbooster.com>`.
+- Once you have verified your changes, commit them to a non-main branch using the `--no-verify` option and push to the current branch.
+  - Follow conventional commits; your commit message should start with `feat:`, `fix:`, etc.
+  - If not specified, make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Cursor) <agent@willbooster.com>`.
   - Always create new commits. Avoid using `--amend`.
 
 ## Coding Style
 
-- Write comments that explain "why" rather than "what". Avoid explanations that can be understood from the code itself.
-- Use stderr for logging debug messages temporarily since stdout output is sometimes omitted.
-- When adding new functions or classes, define them below any functions or classes that call them to maintain clear call order.
-- Prefer `undefined` over `null` unless explicitly dealing with APIs or libraries that require `null`.
-- Always perform existence checks on array due to `noUncheckedIndexedAccess: true`.
+- Simplify code as much as possible to eliminate redundancy.
+- Design each module with high cohesion, grouping related functionality together.
+  - Refactor existing large modules into smaller, focused modules when necessary.
+  - Create well-organized directory structures with low coupling and high cohesion.
+- When adding new functions or classes, define them below any functions or classes that call them to maintain a clear top-down call order.
+- Write comments that explain "why" rather than "what". Avoid stating what can be understood from the code itself.
+- Prefer `undefined` over `null` unless explicitly required by APIs or libraries.
diff --git a/.husky/pre-commit b/.husky/pre-commit
diff --git a/.husky/pre-push b/.husky/pre-push
diff --git a/.lefthook/post-merge/prepare.sh b/.lefthook/post-merge/prepare.sh
@@ -1,3 +1,5 @@
+#!/bin/bash
+
 changed_files="$(git diff-tree -r --name-only --no-commit-id ORIG_HEAD HEAD)"
 
 run_if_changed() {
@@ -6,7 +8,5 @@ run_if_changed() {
   fi
 }
 
-run_if_changed "\..+-version" "awk '{print \$1}' .tool-versions | xargs -I{} asdf plugin add {}"
-run_if_changed "\..+-version" "asdf plugin update --all"
-run_if_changed "\..+-version" "asdf install"
+run_if_changed "(mise\.toml|\.mise\.toml|\.tool-versions|\..+-version)" "mise install"
 run_if_changed "package\.json" "yarn"
diff --git a/.lefthook/pre-push/check.sh b/.lefthook/pre-push/check.sh
@@ -0,0 +1 @@
+yarn run typecheck
diff --git a/AGENTS.md b/AGENTS.md
@@ -2,23 +2,26 @@
 
 - Name: @exercode/problem-utils
 - Description: :100: A set of utilities for judging programs on Exercode (https://exercode.willbooster.com/).
-- Package Manager: yarn
+- Package Manager: yarn on zsh
 
 ## General Instructions
 
+- Create a new branch if the current branch is `main`.
 - Do not write tests unless explicitly requested.
 - When fixing tests, gather debug information through logging and screenshots before modifying the code.
-- 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.
+- After making code changes, run `yarn check-all-for-ai` to execute all tests (takes up to 1 hour), or run `yarn check-for-ai` for type checking and linting only (takes up to 10 minutes).
   - If you are confident your changes will not break any tests, you may use `check-for-ai`.
-- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
-  - Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
-  - Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>`.
+- Once you have verified your changes, commit them to a non-main branch using the `--no-verify` option and push to the current branch.
+  - Follow conventional commits; your commit message should start with `feat:`, `fix:`, etc.
+  - If not specified, make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>`.
   - Always create new commits. Avoid using `--amend`.
 
 ## Coding Style
 
-- Write comments that explain "why" rather than "what". Avoid explanations that can be understood from the code itself.
-- Use stderr for logging debug messages temporarily since stdout output is sometimes omitted.
-- When adding new functions or classes, define them below any functions or classes that call them to maintain clear call order.
-- Prefer `undefined` over `null` unless explicitly dealing with APIs or libraries that require `null`.
-- Always perform existence checks on array due to `noUncheckedIndexedAccess: true`.
+- Simplify code as much as possible to eliminate redundancy.
+- Design each module with high cohesion, grouping related functionality together.
+  - Refactor existing large modules into smaller, focused modules when necessary.
+  - Create well-organized directory structures with low coupling and high cohesion.
+- When adding new functions or classes, define them below any functions or classes that call them to maintain a clear top-down call order.
+- Write comments that explain "why" rather than "what". Avoid stating what can be understood from the code itself.
+- Prefer `undefined` over `null` unless explicitly required by APIs or libraries.
diff --git a/CLAUDE.md b/CLAUDE.md
@@ -2,23 +2,26 @@
 
 - Name: @exercode/problem-utils
 - Description: :100: A set of utilities for judging programs on Exercode (https://exercode.willbooster.com/).
-- Package Manager: yarn
+- Package Manager: yarn on zsh
 
 ## General Instructions
 
+- Create a new branch if the current branch is `main`.
 - Do not write tests unless explicitly requested.
 - When fixing tests, gather debug information through logging and screenshots before modifying the code.
-- 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.
+- After making code changes, run `yarn check-all-for-ai` to execute all tests (takes up to 1 hour), or run `yarn check-for-ai` for type checking and linting only (takes up to 10 minutes).
   - If you are confident your changes will not break any tests, you may use `check-for-ai`.
-- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
-  - Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
-  - Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>`.
+- Once you have verified your changes, commit them to a non-main branch using the `--no-verify` option and push to the current branch.
+  - Follow conventional commits; your commit message should start with `feat:`, `fix:`, etc.
+  - If not specified, make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>`.
   - Always create new commits. Avoid using `--amend`.
 
 ## Coding Style
 
-- Write comments that explain "why" rather than "what". Avoid explanations that can be understood from the code itself.
-- Use stderr for logging debug messages temporarily since stdout output is sometimes omitted.
-- When adding new functions or classes, define them below any functions or classes that call them to maintain clear call order.
-- Prefer `undefined` over `null` unless explicitly dealing with APIs or libraries that require `null`.
-- Always perform existence checks on array due to `noUncheckedIndexedAccess: true`.
+- Simplify code as much as possible to eliminate redundancy.
+- Design each module with high cohesion, grouping related functionality together.
+  - Refactor existing large modules into smaller, focused modules when necessary.
+  - Create well-organized directory structures with low coupling and high cohesion.
+- When adding new functions or classes, define them below any functions or classes that call them to maintain a clear top-down call order.
+- Write comments that explain "why" rather than "what". Avoid stating what can be understood from the code itself.
+- Prefer `undefined` over `null` unless explicitly required by APIs or libraries.
diff --git a/GEMINI.md b/GEMINI.md
@@ -2,23 +2,26 @@
 
 - Name: @exercode/problem-utils
 - Description: :100: A set of utilities for judging programs on Exercode (https://exercode.willbooster.com/).
-- Package Manager: yarn
+- Package Manager: yarn on zsh
 
 ## General Instructions
 
+- Create a new branch if the current branch is `main`.
 - Do not write tests unless explicitly requested.
 - When fixing tests, gather debug information through logging and screenshots before modifying the code.
-- 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.
+- After making code changes, run `yarn check-all-for-ai` to execute all tests (takes up to 1 hour), or run `yarn check-for-ai` for type checking and linting only (takes up to 10 minutes).
   - If you are confident your changes will not break any tests, you may use `check-for-ai`.
-- Once you have verified your changes, commit them to the non-main branch using the `--no-verify` option and push to the current branch.
-  - Follow conventional commits, i.e., your commit message should start with `feat:`, `fix:`, etc.
-  - Make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Gemini CLI) <agent@willbooster.com>`.
+- Once you have verified your changes, commit them to a non-main branch using the `--no-verify` option and push to the current branch.
+  - Follow conventional commits; your commit message should start with `feat:`, `fix:`, etc.
+  - If not specified, make sure to add a new line at the end of your commit message with: `Co-authored-by: WillBooster (Gemini CLI) <agent@willbooster.com>`.
   - Always create new commits. Avoid using `--amend`.
 
 ## Coding Style
 
-- Write comments that explain "why" rather than "what". Avoid explanations that can be understood from the code itself.
-- Use stderr for logging debug messages temporarily since stdout output is sometimes omitted.
-- When adding new functions or classes, define them below any functions or classes that call them to maintain clear call order.
-- Prefer `undefined` over `null` unless explicitly dealing with APIs or libraries that require `null`.
-- Always perform existence checks on array due to `noUncheckedIndexedAccess: true`.
+- Simplify code as much as possible to eliminate redundancy.
+- Design each module with high cohesion, grouping related functionality together.
+  - Refactor existing large modules into smaller, focused modules when necessary.
+  - Create well-organized directory structures with low coupling and high cohesion.
+- When adding new functions or classes, define them below any functions or classes that call them to maintain a clear top-down call order.
+- Write comments that explain "why" rather than "what". Avoid stating what can be understood from the code itself.
+- Prefer `undefined` over `null` unless explicitly required by APIs or libraries.
diff --git a/lefthook.yml b/lefthook.yml
@@ -0,0 +1,20 @@
+post-merge:
+  scripts:
+    prepare.sh:
+      runner: bash
+pre-push:
+  scripts:
+    check.sh:
+      runner: bash
+pre-commit:
+  commands:
+    cleanup:
+      glob: '*.{cjs,css,cts,htm,html,js,json,json5,jsonc,jsx,md,mjs,mts,scss,ts,tsx,vue,yaml,yml}'
+      run: yarn run cleanup && git add {staged_files}
+    check-migrations:
+      glob: '**/migration.sql'
+      run: |-
+        if grep -q 'Warnings:' {staged_files}; then
+          echo "Migration SQL files ({staged_files}) contain warnings! Please solve the warnings and commit again."
+          exit 1
+        fi
diff --git a/package.json b/package.json
@@ -32,20 +32,17 @@
   "scripts": {
     "build": "build-ts lib --input src/index.ts src/presets/*.ts",
     "check-all-for-ai": "yarn check-for-ai && yarn test",
-    "check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn lint-fix --quiet && yarn typecheck",
+    "check-for-ai": "yarn install > /dev/null && yarn format > /dev/null 2> /dev/null || true && yarn typecheck && yarn lint-fix --quiet",
     "cleanup": "yarn format && yarn lint-fix",
     "format": "sort-package-json && yarn prettify",
-    "postinstall": "husky || true",
     "lint": "eslint --color",
     "lint-fix": "yarn lint --fix",
-    "prepack": "pinst --disable",
-    "postpack": "pinst --enable",
-    "prepare": "husky || true",
+    "prepare": "lefthook install || true",
     "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}\" \"!**/test{-,/}fixtures/**\" || true",
     "start": "build-ts run src/index.ts",
     "test": "rm -fr temp && dotenv -c test -- vitest test",
     "test/ci-setup": "yarn build && bun install --cwd example",
-    "typecheck": "tsc --noEmit --Pretty"
+    "typecheck": "tsc --noEmit"
   },
   "prettier": "@willbooster/prettier-config",
   "dependencies": {
@@ -66,7 +63,7 @@
     "build-ts": "17.0.17",
     "conventional-changelog-conventionalcommits": "9.1.0",
     "dotenv-cli": "11.0.0",
-    "eslint": "9.39.1",
+    "eslint": "9.39.2",
     "eslint-config-flat-gitignore": "2.1.0",
     "eslint-config-prettier": "10.1.8",
     "eslint-import-resolver-typescript": "4.4.4",
@@ -76,10 +73,9 @@
     "eslint-plugin-unicorn": "62.0.0",
     "eslint-plugin-unused-imports": "4.3.0",
     "globals": "17.3.0",
-    "husky": "9.1.7",
+    "lefthook": "2.1.0",
     "lint-staged": "16.2.7",
     "micromatch": "4.0.8",
-    "pinst": "3.0.0",
     "prettier": "3.8.1",
     "prettier-plugin-java": "2.8.1",
     "puppeteer": "24.36.1",
diff --git a/yarn.lock b/yarn.lock
