precheck
Skill240 starsChanged 19 days agoMITView on GitHub
PR 作成前の lint + format + test 一括実行。引数で scope (python/rust/cs/go/js/cpp/all) を指定可能。未指定なら git diff から自動判定。
1 other project uses a version of this.
Adopted by
Most recently taken up by
- OffchainLabs/prysmtheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- OffchainLabs/prysm★ 3.8ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- bump-depsSkill
- check-cross-runtimeSkill
- check-loanwordSkill
- check-new-runtime-assetSkill
- check-pr-readySkill
- check-puaSkill
- check-review-backlogSkill
- check-runtime-paritySkill
- commitSkill
- create-prSkill
- prepare-releaseSkill
- publish-modelSkill
- release-prepSkill
- reply-reviewSkill
- run-testsSkill
- skill-healthSkill
- sync-docsSkill
- watch-ci-patternsSkill
- watch-prSkill
The file
Files
Pre-commit / Pre-PR チェック
$ARGUMENTS で指定されたスコープに対して、CI が実行するチェックと同等の検査をローカルで実行します。
変更ファイル
!git diff --name-only HEAD 2>/dev/null | head -30
スコープ判定
引数 $ARGUMENTS:
python→ src/python/ + src/python_run/ (ruff は CI と同じく repo 全体の.pyが対象。scripts//tests//docker/等の変更も python scope とみなす)rust→ src/rust/ のみcs→ src/csharp/ のみgo→ src/go/ のみjs→ src/wasm/openjtalk-web/ のみcpp→ src/cpp/ のみall→ 全ランタイム- (空) → 上記の
git diffの結果からスコープを推定 (複数該当ならそれら全て)
実行ステップ (該当スコープのみ)
Python
# Lint (CI の lint-gates.yml python-lint step と同じく repo 全体。 除外は pyproject.toml の [tool.ruff])
uv run ruff check
# Format check
uv run ruff format --check
# Unit tests (runtime + g2p)
cd src/python_run && uv run pytest tests/ -o addopts="" --tb=short -q && cd ../..Rust
cd src/rust
cargo fmt --all -- --check
cargo clippy --workspace --all-features -- -D warnings
cargo test -p piper-plus --no-fail-fast
cd ../..C# (.NET)
dotnet build src/csharp/PiperPlus.sln -c Release --nologo
dotnet format src/csharp/PiperPlus.sln --verify-no-changes --no-restore
dotnet test src/csharp/PiperPlus.sln -c Release --no-build --nologo --verbosity minimalGo
cd src/go
go vet ./... ./phonemize/...
go test -race -count=1 ./... ./phonemize/...
cd ../..JavaScript / WASM
cd src/wasm/openjtalk-web
npm run test:npm-package:all
cd ../../..C++
cmake --build build --config Release
ctest --test-dir build -C Release --output-on-failure報告フォーマット
各ステップ完了後、以下の形式で結果を報告:
## Precheck 結果
| ステップ | 結果 | 詳細 |
|---------|------|------|
| Python ruff check | ✅ / ❌ | (失敗時はエラー要約) |
| Python ruff format | ✅ / ❌ | |
| Python pytest | ✅ / ❌ | (passed/failed/skipped カウント) |
| ... | ... | ... |失敗時の対応
- ruff format 失敗 →
uv run ruff formatで自動修正 - ruff check 失敗 →
uv run ruff check --fixで自動修正 - pytest 失敗 → 失敗テストの最初の 3 件を要約して原因候補を提示
- dotnet format 失敗 →
dotnet format src/csharp/PiperPlus.slnで自動修正
注意
- pytest.ini に
--covが含まれていて pytest-cov が無い環境では-o addopts=""で上書きする (CLAUDE.md memory) - 学習ジョブや巨大ベンチマークは実行しない (unit/integration のみ)
- 1 ステップでも失敗したら以降のステップは実行せず即報告 (
set -e相当)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

