メニュー
Complete workflow for upgrading the prebuilt LLVM packages clice depends on — build-llvm CI, API adaptation, release-llvm pruning, changelog. Arg = target version, e.g. 22.1.4.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/clice-io/clice --skill upgrade-llvmコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | upgrade-llvm |
| description | Complete workflow for upgrading the prebuilt LLVM packages clice depends on — build-llvm CI, API adaptation, release-llvm pruning, changelog. Arg = target version, e.g. 22.1.4. |
Upgrade LLVM to a new version. Accepts the target version as argument (e.g., 22.1.4).
This is the complete workflow for upgrading the LLVM prebuilt packages that clice depends on. Follow each step in order. Steps that involve CI should use polling (check every ~5 minutes) to wait for completion.
Trigger the build-llvm workflow on GitHub Actions:
gh workflow run build-llvm.yml \
--field llvm_version="<VERSION>"
Download the artifact matching the development machine:
gh run view <RUN_ID>
gh run download <RUN_ID> -n x86_64-unknown-linux-gnu.releasedbg.tar.xz -D .llvm-download
mkdir -p .llvm
tar -xf .llvm-download/x86_64-unknown-linux-gnu.releasedbg.tar.xz -C .llvm
Configure clice to build against it:
pixi run cmake-config RelWithDebInfo ON -- "-DLLVM_INSTALL_PATH=.llvm"
pixi run cmake-build RelWithDebInfo
Compilation will likely fail — that's what Step 3 addresses.
Fix LLVM API breaking changes based on compilation errors. Common categories:
clang/Driver/Options.h → clang/Options/Options.hclang::driver::options → clang::optionscreateDiagnostics parameter changesStrategy:
pixi run unit-test RelWithDebInfo passesWhen a fix is not obvious, read the LLVM source code to understand the new API. If ../llvm-project exists locally, use it. Otherwise, look up the upstream commit/PR on GitHub.
git checkout -b chore/upgrade-llvm-XX
git add -A
git commit -m "chore: upgrade LLVM to XX.Y.Z"
git push -u origin chore/upgrade-llvm-XX
gh pr create --title "chore: upgrade LLVM to XX.Y.Z" --body "..."
CI will fail at this point (manifest hashes are stale) — this is expected.
Trigger release-llvm to build pruned packages:
gh workflow run release-llvm.yml \
--ref <BRANCH> \
--field source_run_id="<STEP1_RUN_ID>" \
--field llvm_version="<VERSION>"
This will: discover unused libs → create clice-llvm release → repackage with pruning. Poll until complete.
Update the version string in cmake/package.cmake:
setup_llvm("<VERSION>")
Commit and push:
git add cmake/package.cmake
git commit -m "chore: update LLVM to <VERSION>"
git push
Poll CI until all platforms pass. CMake downloads the correct artifact automatically based on the version and platform — no manifest file needed.
Every LLVM upgrade MUST append to docs/en/changelog/llvm-changelog.md.
Add a new H2 section (e.g., ## LLVM 22 → 23) documenting all breaking changes encountered. For each API change, record:
https://github.com/llvm/llvm-project/pull/<NUM>)To find upstream commits, search the LLVM git history between version tags:
# If ../llvm-project exists locally:
cd ../llvm-project
git log --oneline llvmorg-<OLD>..llvmorg-<NEW> -- clang/include/clang/AST/
If the LLVM source is not available locally, look up changes on GitHub by searching the LLVM repository commit history.
Group changes by category (Type System, NNS, Driver/Frontend, Other) with a table per category. See the existing LLVM 21 → 22 section as a template.
Present a summary to the user and wait for confirmation before considering the upgrade complete. The summary should include:
The user decides whether all changes are acceptable or if adjustments are needed. Do NOT push final changes or mark the work as done until the user confirms.
build-llvm.py. Users must use our packaged LLVM.