bump-deps
Skill240 starsChanged 5 days agoMITView on GitHub
ORT / openjtalk / ruff のような cross-runtime に canonical sync が必要な依存関係を 1 コマンドで bump する read-mostly skill。 既存の `check_ort_versions.py` / `check_openjtalk_version_sync.py` / `check_ruff_version_sync.py` が drift 検出後に「どこを何バージョンに上げる」を提示する逆方向 helper。
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tounsils/claude-code-skillstheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tounsils/claude-code-skills★ 1same 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
- check-cross-runtimeSkill
- check-loanwordSkill
- check-new-runtime-assetSkill
- check-pr-readySkill
- check-puaSkill
- check-review-backlogSkill
- check-runtime-paritySkill
- commitSkill
- create-prSkill
- precheckSkill
- prepare-releaseSkill
- publish-modelSkill
- release-prepSkill
- reply-reviewSkill
- run-testsSkill
- skill-healthSkill
- sync-docsSkill
- watch-ci-patternsSkill
- watch-prSkill
The file
Files
Cross-Runtime Dependency Bump Skill
ORT / openjtalk / ruff のような「複数ファイル散在 / canonical source あり」 系の依存関係を、 canonical を更新したら mirror 箇所も同時に提案する skill。
既存の sync gate (check_*_sync.py) は drift を検出するだけ、 本 skill は drift を 解消する diff を提示する。
memory feedback_conservative_changes.md に従い、 デフォルト dry-run、 markdown diff の提示のみ。 --apply で Edit を実行。
対象依存
| 名前 | Canonical | Mirror 数 | 既存 gate |
| ONNX Runtime | cmake/OnnxRuntime.cmake (ONNXRUNTIME_VERSION) | 6+ ファイル | check_ort_versions.py / check_ort_version_drift.py |
| openjtalk | cmake/ExternalDeps.cmake (URL 内の version) | 3+ ファイル | check_openjtalk_version_sync.py |
| ruff | pyproject.toml (dev group の最初の出現) | checker が検出する全 pin site | check_ruff_version_sync.py |
| (将来) | cmake/... (新 dep) | TBD | (新 gate) |
引数
$1(必須):ort/openjtalk/ruff/all--target X.Y.Z(必須): 新 version--apply: dry-run の確認後 Edit を実行 (default は dry-run)
現在の状態
- ブランチ: !
git rev-parse --abbrev-ref HEAD - 引数: $ARGUMENTS
フェーズ 1: 現状 + drift 確認
uv run python scripts/check_ort_versions.py --verbose 2>&1 | head -30
uv run python scripts/check_openjtalk_version_sync.py 2>&1 | head -20
uv run python scripts/check_ruff_version_sync.py 2>&1 | head -20drift があれば「先に解消」を提案、 なければ「新 target への bump 案」を作る。
フェーズ 2: ORT bump 案 (ort の場合)
# 対象一覧の正本は scripts/check_ort_versions.py の EXACT_TARGETS / FLOOR_TARGETS
CURRENT=$(rg -o 'ONNXRUNTIME_VERSION "([0-9.]+)"' -r '$1' cmake/OnnxRuntime.cmake) # 現在値 (例 1.20.0)
TARGET="$2" # 例 1.21.0
# 1. cmake/OnnxRuntime.cmake (canonical) + cmake/find_onnxruntime_windows.cmake
rg "set\(ONNXRUNTIME_VERSION" cmake/
# 2. .github/workflows/ の exact-match 対象 7 本
# env 変数 `ONNXRUNTIME_VERSION:` を持つもの:
# release-shared-lib / android-build / release-kotlin-g2p / kotlin-g2p-ci / bundle-size-gate
# URL / cache key に version を直書きしているもの:
# build-piper / _build-test-cpp
rg -F "$CURRENT" .github/workflows/{release-shared-lib,android-build,release-kotlin-g2p,kotlin-g2p-ci,bundle-size-gate,build-piper,_build-test-cpp}.yml
# 3. docker/cpp-dev/Dockerfile (URL 直書き)
rg -F "$CURRENT" docker/cpp-dev/Dockerfile
# 4. Python floor pin: src/python/pyproject.toml + src/python_run/{pyproject.toml,requirements_gpu.txt}
rg "onnxruntime(-gpu)?[<>=~]" src/python/pyproject.toml src/python_run/pyproject.toml src/python_run/requirements_gpu.txt
# 5. src/csharp/*.csproj
rg "Microsoft.ML.OnnxRuntime" src/csharp/
# 6. src/go/go.mod
rg "github.com/yalue/onnxruntime_go" src/go/go.mod
# 7. src/wasm/openjtalk-web/package.json
rg "onnxruntime-web" src/wasm/openjtalk-web/各 hit の前後を markdown diff 形式で出力:
- set(ONNXRUNTIME_VERSION "1.20.0")
+ set(ONNXRUNTIME_VERSION "1.21.0")フェーズ 3: openjtalk bump 案 (openjtalk の場合)
cmake/ExternalDeps.cmake の PYOPENJTALK_PLUS_URL (PyPI sdist、 例えば pyopenjtalk_plus-0.4.1.post8.tar.gz) と URL_HASH SHA256= (2 箇所) を更新し、 repo 内の全 pyproject.toml / requirements*.txt の pyopenjtalk-plus 指定 (例: src/python_run/requirements.txt の pyopenjtalk-plus>=0.4.1.post8、 src/python/g2p/pyproject.toml の >=0.3,<1) が新 version を許容するか確認する。 check_openjtalk_version_sync.py は == / ~= 違反を ERROR、 範囲指定の違反を WARN として扱う。
フェーズ 4: ruff bump 案 (ruff の場合)
5 箇所同時更新 (scripts/check_ruff_version_sync.py の EXPECTED_PIN_COUNT と一致):
.pre-commit-config.yamlrev: v<VER>(astral-sh/ruff-pre-commit).github/workflows/lint-gates.ymlpip install ruff==<VER>(python-lint step)pyproject.toml3 dependency group の"ruff==<VER>"
.github/workflows/ci.yml は PR #462 で ruff job を削除済みのため pin site ではない。
フェーズ 5: 再検証
--apply で Edit を実行した後、 同じ check_*_sync.py を再走させて drift 0 を確認:
uv run python scripts/check_ort_versions.py
uv run python scripts/check_openjtalk_version_sync.py
uv run python scripts/check_ruff_version_sync.pyフェーズ 6: 追加検証 (ORT の場合)
ORT bump は ABI 変更があり得るため、 以下の dependent check も走らせる:
# Python load test
uv run python -c "import onnxruntime; print(onnxruntime.__version__)"
# Rust load test
(cd src/rust && cargo check -p piper-plus)
# 各 runtime CI workflow が pass しているか
gh run list --workflow=ci.yml --limit 5注意
- memory feedback_conservative_changes: ORT は ABI 互換が崩れやすいため、 patch bump (
0.0.X) のみ default、 minor / major bump は明示--target指定必須。 - memory feedback_pin_actions_sha: actions の SHA pin に類する操作はこの skill では行わない (action の pin は pre-commit / lint-gates の
action-pin-gate=scripts/check_action_pins.pyが検査する)。 - memory feedback_merge_caution:
--applyで Edit を実行する時はファイル単位で confirm。
使用例
# ORT を 1.21.0 に bump (dry-run)
/bump-deps ort --target 1.21.0
# ruff を 0.16.0 に bump して即適用
/bump-deps ruff --target 0.16.0 --apply
# openjtalk patch bump
/bump-deps openjtalk --target 0.4.1.post9期待効果
- ORT / openjtalk / ruff の bump 漏れ を check_*_sync.py に頼らず能動的に防ぐ
- canonical source → mirror への 手作業 grep + Edit を 1 skill 化
- Dependabot uv-workspace PR (pyproject.toml だけ bump) のような partial bump に対する後追い fix
- ABI 互換確認の post-bump dependent check
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.

