[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BZFEQ2NCYCKQX0RTMQM55A":3,"skill-same:01M6BZFEQ2NCYCKQX0RTMQM55A":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6BZFEQ2NCYCKQX0RTMQM55A","upgrade-llvm",null,"Read before upgrading xclang\u002FLLVM (arg = the xclang version, e.g. 23.1.2.1), touching MODULE.bazel, .bazelrc, BUILD.bazel or bazel\u002F, or regenerating modules\u002F — after a library bump, or when clice needs a header or macro it does not export.","clice-io\u002Fclice","clice-io","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F176553789?v=4","01M6BZEJH3SKDZ3SMSS1V6CKKB","clice","01M6BZEJN97S3AQVRQ4V7GGE5C",1383,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fupgrade-llvm\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"upgrade llvm","llvm","upgrade","library","macro","bazel","modules","bump","module","when","version","build","read","export","it","2026-11-10 10:12:30",false,"---\nname: upgrade-llvm\ndescription: Read before upgrading xclang\u002FLLVM (arg = the xclang version, e.g. 23.1.2.1), touching MODULE.bazel, .bazelrc, BUILD.bazel or bazel\u002F, or regenerating modules\u002F — after a library bump, or when clice needs a header or macro it does not export.\n---\n\nUpgrade LLVM to a new version. Accepts the xclang version as argument (e.g., `23.1.2.1`: LLVM 23.1.2, xclang's first build of it).\n\nThe compiler clice builds with and the LLVM\u002FClang libraries it links both come from one [xclang](https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fxclang) release: xclang's Bazel module (registry https:\u002F\u002Fbazel.clice.io) brings the toolchain and the release's `libclang-\u003Cversion>-\u003Ctriple>[-asan].tar.xz` archives as repositories, and the conda package `xclang` (channel `https:\u002F\u002Fconda.clice.io`) the LLVM tools the tests and the packaging run. They always move together: the archives hold ThinLTO bitcode, which only the LLVM that wrote it is sure to read. clice imports libclang's headers, with every other third-party library's, through the generated module in `modules\u002F`, so an upgrade regenerates it before anything builds. Follow each step in order.\n\n**Read `toolchain-changelog.md` in this directory before touching `MODULE.bazel`, `.bazelrc`, `BUILD.bazel` or `bazel\u002F`**: it records the platform pitfalls that still apply (symptom, cause, fix, how to check). Every new one is added there in the same shape; a toolchain change without an entry is not finished.\n\nThe work happens on a branch `chore\u002Fupgrade-llvm-\u003Cmajor>`, created from fresh `origin\u002Fmain` (CLAUDE.md) before Step 2, and runs on two boxes (the agent-box skill), leased once and kept for the whole upgrade: a Linux one, which regenerates `modules\u002F` for every configuration and cross-builds arm64 Linux and both Windows targets as CI does, and a macOS one, which builds its own and x64 macOS.\n\n## Step 1: The xclang Release\n\nThe toolchain and the libraries are built in the xclang repository, by its own pipeline; a new LLVM version there is a change of its `LLVM_VERSION` and sources, and ends with a release tagged `\u003Cllvm version>.\u003Crevision>`, the conda packages on conda.clice.io and the Bazel module on bazel.clice.io. Upgrading clice starts once that release exists:\n\n```bash\ngh release view \u003CVERSION> -R clice-io\u002Fxclang --json assets --jq '.assets[].name' | grep libclang\n```\n\nEvery target clice builds needs its `libclang-\u003CVERSION>-\u003Ctriple>.tar.xz`, and the Debug builds (x86_64 Linux, arm64 macOS) their `-asan` archives.\n\n## Step 2: A clice to Regenerate With\n\nOn the Linux box, build clice from this tree before any pin moves, and keep it aside:\n\n```bash\npixi run build RelWithDebInfo\nrm -rf ~\u002Fclice-bin && cp -RL build\u002FRelWithDebInfo\u002Fbin ~\u002Fclice-bin\n```\n\nThe new headers need not build the old `modules\u002F` (a name it exports may be gone upstream), and regenerating only reads them. But the clice must carry this tree's own `clice modularize`: one built from an older tree writes another shape (thousands of extra lines of enum wrappers). main's CI build artifact (`build-\u003Ctriple>-RelWithDebInfo`, kept 3 days) serves as well: unpacked into `~\u002Fclice-bin`, it needs `chmod +x ~\u002Fclice-bin\u002Fbin\u002F*` (artifacts drop the executable bit), and a box that skips the build needs `pixi run install-tests` before Step 4, or `npx bazel` gets a 404.\n\n## Step 3: Pin It\n\nMove every pin in one change:\n\n- `MODULE.bazel`: `bazel_dep(name = \"xclang\", version = \"\u003CVERSION>\")`\n- `pixi.toml`: every `xclang = \"==\u003CVERSION>\"`, and the Windows test environments' `llvm-tools = \"==\u003CLLVM version>\"`\n- `pixi.lock`: `pixi lock`\n\nEvery file of the toolchain and of libclang is an input of the actions that read it, so the new release rebuilds everything; nothing has to be cleaned. A release re-published under the same tag needs a new module version on the registry (its archive digests are recorded there).\n\n## Step 4: Regenerate `modules\u002F`\n\n`modules\u002Fdemand.cpp` records what clice takes from the libraries; `scripts\u002Fmodules.py` builds it for a configuration, indexes it with clice and wraps the libraries' headers with `clice modularize`, then merges the eight configurations into `modules\u002F`. Push the pinned tree to the Linux box, then:\n\n```bash\nbox run $linux 'pixi run python scripts\u002Fmodules.py --clice ~\u002Fclice-bin\u002Fbin\u002Fclice generate'\nbox run $linux 'pixi run python scripts\u002Fmodules.py --clice ~\u002Fclice-bin\u002Fbin\u002Fclice merge'\nbox cp $linux . modules\n```\n\nEach configuration takes about half a minute. The macOS ones compile against Apple's SDK, which the first of them fetches (`MODULE.bazel` accepts its license). Nothing under `modules\u002F` but `demand.cpp`, `BUILD.bazel` and `modules.bzl` is edited by hand; a wrong result is fixed in its inputs and regenerated:\n\n- `generate` compiles `demand.cpp` first, so a header that moved or went upstream stops it there: fix the include in `demand.cpp`, as the API adaptation of Step 5 would in clice's own files.\n- A warning from `clice modularize` stops it too: a header the partition leaves to the program means a library's include directory moved (the partition's globs are in `scripts\u002Fmodules.py`).\n- What only some configurations export lands under their conditions in `third_party.cppm` and `libc.cppm`; what clice uses on one platform alone is written under that platform's `#ifdef` in `demand.cpp` (`llvm\u002FSupport\u002FWindowsError.h` under `_WIN32`).\n\nThe diff of `modules\u002F` is part of the upgrade's review: names the libraries dropped or renamed, and macros that changed.\n\n## Step 5: Build and Adapt the API\n\n```bash\npixi run build RelWithDebInfo\n```\n\nFix LLVM API breaking changes based on compilation errors. Common categories:\n\n- **Header path changes**: e.g., `clang\u002FDriver\u002FOptions.h` → `clang\u002FOptions\u002FOptions.h`\n- **Namespace migrations**: e.g., `clang::driver::options` → `clang::options`\n- **Type system changes**: e.g., ElaboratedType removal, NestedNameSpecifier pointer→value\n- **Function signature changes**: e.g., `createDiagnostics` parameter changes\n- **Type merges\u002Fsplits**: e.g., DependentTemplateSpecializationType → TemplateSpecializationType\n\nStrategy:\n\n1. Fix header\u002Fnamespace changes first (mechanical). A header, name or macro clice now needs that `modules\u002F` does not export goes into `demand.cpp`, and Step 4 runs again.\n2. Fix type system and signature changes (requires understanding semantics)\n3. Update the case outputs upstream changed: `UPDATE_SNAPSHOTS=1`, every changed block reviewed like code (the write-tests skill)\n4. Ensure `pixi run -e test-run unit-test RelWithDebInfo` passes\n5. Port `clang\u002Flib\u002FAST\u002FStmtProfile.cpp` changes into `src\u002Fsemantic\u002Fexpr_hash.cpp` (a trimmed copy of `StmtProfiler` with clice's own leaves): do not diff the files — list the upstream commits with `git log llvmorg-\u003Cold>..llvmorg-\u003Cnew> -- clang\u002Flib\u002FAST\u002FStmtProfile.cpp`, and hand an Opus subagent that list with the instruction to apply each commit's C and C++ visitor changes to the port; `unittests --test-filter=expr_hash` (the bit-for-bit fidelity test against `Stmt::Profile`) must be green afterwards\n6. Bump `index_format_version` in `src\u002Findex\u002Fformat.cppm`: entity hashes (`src\u002Fsemantic\u002Fidentity.cpp`) follow clang's canonicalization rules, so they can change silently across versions and an old index would otherwise keep serving stale symbols\n7. A library clice starts using directly is added to `LLVM_LIBRARIES` in `bazel\u002FBUILD.bazel`. xclang's libclang archives carry only the libraries clice uses: one they lack goes into xclang's `toolchain\u002Fcmake\u002Fcaches\u002Fclang.cmake` (`LLVM_Development_DISTRIBUTION_COMPONENTS`) first, and needs a new xclang release\n\nWhen a fix is not obvious, read the LLVM source code to understand the new API. If `..\u002Fllvm-project` exists locally, use it. Otherwise, look up the upstream commit\u002FPR on GitHub.\n\nThen the unit tests and the cases on the Linux box, and a build of every other configuration on the box that builds it: `pixi run build Debug` on both boxes (the ASan libclang, built with assertions, declares more than the release one), `pixi run build RelWithDebInfo` on macOS, and `pixi run build RelWithDebInfo -- --platforms=@xclang\u002F\u002Fplatforms:\u003Ctriple>` for the cross ones. CI runs them all, but a configuration that does not build is found faster here.\n\n## Step 6: Write the Changelogs (REQUIRED)\n\nToolchain-level findings on clice's side (`MODULE.bazel`, `.bazelrc`, `BUILD.bazel`, `bazel\u002F`, CI mechanics; the toolchain itself keeps its own notes in xclang) go to `toolchain-changelog.md` in this directory, in its symptom \u002F cause \u002F fix \u002F check shape. API changes go to `llvm-changelog.md`, maintainer reference material, deliberately not a docs page.\n\nEvery LLVM upgrade adds a new H2 section to `llvm-changelog.md` (e.g., `## LLVM 22 → 23`) documenting all breaking changes encountered. For each API change, record:\n\n- Change description\n- Upstream commit hash\n- PR number (link to `https:\u002F\u002Fgithub.com\u002Fllvm\u002Fllvm-project\u002Fpull\u002F\u003CNUM>`)\n- Impact on clice\n\nTo find upstream commits, search the LLVM git history between version tags (`git log --oneline llvmorg-\u003COLD>..llvmorg-\u003CNEW> -- clang\u002Finclude\u002Fclang\u002FAST\u002F` in `..\u002Fllvm-project`, or the GitHub history). Group changes by category with a table per category, as the newest section does.\n\n## Step 7: Report and Wait\n\nPresent a summary to the maintainer and **wait for confirmation** before opening the PR. The summary should include:\n\n- All API changes that were adapted and how they were resolved\n- What the regenerated `modules\u002F` dropped, and what `demand.cpp` gained\n- All test expectation changes (snapshot updates, assertion value changes) and why\n- Any unavoidable behavior changes from upstream LLVM (e.g., TypePrinter output differences, type sugar changes) that affect user-visible features like hover\n- The LLVM changelog that was written\n\nThe maintainer decides whether all changes are acceptable or if adjustments are needed.\n\n## Step 8: The PR\n\nThe pr skill takes over; the title is `chore: upgrade LLVM to \u003CX.Y.Z>`.\n\n## Notes\n\n- **Other libraries**: a version bump of kotatsu or any other library `modules\u002F` wraps (its `bazel_dep` in `MODULE.bazel`) is Steps 2 and 4 alone, then the build; so is clice starting to use a header or macro `modules\u002F` does not export yet. A new library is added to `LIBRARIES` in `modules\u002Fmodules.bzl` and to the partition in `scripts\u002Fmodules.py`.\n- **Private headers**: clice includes no private clang headers, and xclang's libclang archives carry none; one clice starts to need goes into xclang's libclang package (`toolchain\u002F` in xclang) first.\n- **Debug builds**: ASan builds (`bazel\u002Fclice.bazelrc`'s Debug) link the ASan libclang, which xclang builds for x86_64 Linux and arm64 macOS (its `@libclang` follows `--features=asan`); the other targets have no Debug build.\n","Upgrade LLVM to a new version. Accepts the xclang version as argument (e.g., `23.1.2.1`: LLVM 23.1.2, xclang's first build of it).\n\nThe compiler clice builds with and the LLVM\u002FClang libraries it links both come from one [xclang](https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fxclang) release: xclang's Bazel module (registry https:\u002F\u002Fbazel.clice.io) brings the toolchain and the release's `libclang-\u003Cversion>-\u003Ctriple>[-asan].tar.xz` archives as repositories, and the conda package `xclang` (channel `https:\u002F\u002Fconda.clice.io`) the LLVM tools the tests and the packaging run. They always move together: the archives hold ThinLTO bitcode, which only the LLVM that wrote it is sure to read. clice imports libclang's headers, with every other third-party library's, through the generated module in `modules\u002F`, so an upgrade regenerates it before anything builds. Follow each step in order.\n\n**Read `toolchain-changelog.md` in this directory before touching `MODULE.bazel`, `.bazelrc`, `BUILD.bazel` or `bazel\u002F`**: it records the platform pitfalls that still apply (symptom, cause, fix, how to check). Every new one is added there in the same shape; a toolchain change without an entry is not finished.\n\nThe work happens on a branch `chore\u002Fupgrade-llvm-\u003Cmajor>`, created from fresh `origin\u002Fmain` (CLAUDE.md) before Step 2, and runs on two boxes (the agent-box skill), leased once and kept for the whole upgrade: a Linux one, which regenerates `modules\u002F` for every configuration and cross-builds arm64 Linux and both Windows targets as CI does, and a macOS one, which builds its own and x64 macOS.\n\n## Step 1: The xclang Release\n\nThe toolchain and the libraries are built in the xclang repository, by its own pipeline; a new LLVM version there is a change of its `LLVM_VERSION` and sources, and ends with a release tagged `\u003Cllvm version>.\u003Crevision>`, the conda packages on conda.clice.io and the Bazel module on bazel.clice.io. Upgrading clice starts once that release exists:\n\n```bash\ngh release view \u003CVERSION> -R clice-io\u002Fxclang --json assets --jq '.assets[].name' | grep libclang\n```\n\nEvery target clice builds needs its `libclang-\u003CVERSION>-\u003Ctriple>.tar.xz`, and the Debug builds (x86_64 Linux, arm64 macOS) their `-asan` archives.\n\n## Step 2: A clice to Regenerate With\n\nOn the Linux box, build clice from this tree before any pin moves, and keep it aside:\n\n```bash\npixi run build RelWithDebInfo\nrm -rf ~\u002Fclice-bin && cp -RL build\u002FRelWithDebInfo\u002Fbin ~\u002Fclice-bin\n```\n\nThe new headers need not build the old `modules\u002F` (a name it exports may be gone upstream), and regenerating only reads them. But the clice must carry this tree's own `clice modularize`: one built from an older tree writes another shape (thousands of extra lines of enum wrappers). main's CI build artifact (`build-\u003Ctriple>-RelWithDebInfo`, kept 3 days) serves as well: unpacked into `~\u002Fclice-bin`, it needs `chmod +x ~\u002Fclice-bin\u002Fbin\u002F*` (artifacts drop the executable bit), and a box that skips the build needs `pixi run install-tests` before Step 4, or `npx bazel` gets a 404.\n\n## Step 3: Pin It\n\nMove every pin in one change:\n\n- `MODULE.bazel`: `bazel_dep(name = \"xclang\", version = \"\u003CVERSION>\")`\n- `pixi.toml`: every `xclang = \"==\u003CVERSION>\"`, and the Windows test environments' `llvm-tools = \"==\u003CLLVM version>\"`\n- `pixi.lock`: `pixi lock`\n\nEvery file of the toolchain and of libclang is an input of the actions that read it, so the new release rebuilds everything; nothing has to be cleaned. A release re-published under the same tag needs a new module version on the registry (its archive digests are recorded there).\n\n## Step 4: Regenerate `modules\u002F`\n\n`modules\u002Fdemand.cpp` records what clice takes from the libraries; `scripts\u002Fmodules.py` builds it for a configuration, indexes it with clice and wraps the libraries' headers with `clice modularize`, then merges the eight configurations into `modules\u002F`. Push the pinned tree to the Linux box, then:\n\n```bash\nbox run $linux 'pixi run python scripts\u002Fmodules.py --clice ~\u002Fclice-bin\u002Fbin\u002Fclice generate'\nbox run $linux 'pixi run python scripts\u002Fmodules.py --clice ~\u002Fclice-bin\u002Fbin\u002Fclice merge'\nbox cp $linux . modules\n```\n\nEach configuration takes about half a minute. The macOS ones compile against Apple's SDK, which the first of them fetches (`MODULE.bazel` accepts its license). Nothing under `modules\u002F` but `demand.cpp`, `BUILD.bazel` and `modules.bzl` is edited by hand; a wrong result is fixed in its inputs and regenerated:\n\n- `generate` compiles `demand.cpp` first, so a header that moved or went upstream stops it there: fix the include in `demand.cpp`, as the API adaptation of Step 5 would in clice's own files.\n- A warning from `clice modularize` stops it too: a header the partition leaves to the program means a library's include directory moved (the partition's globs are in `scripts\u002Fmodules.py`).\n- What only some configurations export lands under their conditions in `third_party.cppm` and `libc.cppm`; what clice uses on one platform alone is written under that platform's `#ifdef` in `demand.cpp` (`llvm\u002FSupport\u002FWindowsError.h` under `_WIN32`).\n\nThe diff of `modules\u002F` is part of the upgrade's review: names the libraries dropped or renamed, and macros that changed.\n\n## Step 5: Build and Adapt the API\n\n```bash\npixi run build RelWithDebInfo\n```\n\nFix LLVM API breaking changes based on compilation errors. Common categories:\n\n- **Header path changes**: e.g., `clang\u002FDriver\u002FOptions.h` → `clang\u002FOptions\u002FOptions.h`\n- **Namespace migrations**: e.g., `clang::driver::options` → `clang::options`\n- **Type system changes**: e.g., ElaboratedType removal, NestedNameSpecifier pointer→value\n- **Function signature changes**: e.g., `createDiagnostics` parameter changes\n- **Type merges\u002Fsplits**: e.g., DependentTemplateSpecializationType → TemplateSpecializationType\n\nStrategy:\n\n1. Fix header\u002Fnamespace changes first (mechanical). A header, name or macro clice now needs that `modules\u002F` does not export goes into `demand.cpp`, and Step 4 runs again.\n2. Fix type system and signature changes (requires understanding semantics)\n3. Update the case outputs upstream changed: `UPDATE_SNAPSHOTS=1`, every changed block reviewed like code (the write-tests skill)\n4. Ensure `pixi run -e test-run unit-test RelWithDebInfo` passes\n5. Port `clang\u002Flib\u002FAST\u002FStmtProfile.cpp` changes into `src\u002Fsemantic\u002Fexpr_hash.cpp` (a trimmed copy of `StmtProfiler` with clice's own leaves): do not diff the files — list the upstream commits with `git log llvmorg-\u003Cold>..llvmorg-\u003Cnew> -- clang\u002Flib\u002FAST\u002FStmtProfile.cpp`, and hand an Opus subagent that list with the instruction to apply each commit's C and C++ visitor changes to the port; `unittests --test-filter=expr_hash` (the bit-for-bit fidelity test against `Stmt::Profile`) must be green afterwards\n6. Bump `index_format_version` in `src\u002Findex\u002Fformat.cppm`: entity hashes (`src\u002Fsemantic\u002Fidentity.cpp`) follow clang's canonicalization rules, so they can change silently across versions and an old index would otherwise keep serving stale symbols\n7. A library clice starts using directly is added to `LLVM_LIBRARIES` in `bazel\u002FBUILD.bazel`. xclang's libclang archives carry only the libraries clice uses: one they lack goes into xclang's `toolchain\u002Fcmake\u002Fcaches\u002Fclang.cmake` (`LLVM_Development_DISTRIBUTION_COMPONENTS`) first, and needs a new xclang release\n\nWhen a fix is not obvious, read the LLVM source code to understand the new API. If `..\u002Fllvm-project` exists locally, use it. Otherwise, look up the upstream commit\u002FPR on GitHub.\n\nThen the unit tests and the cases on the Linux box, and a build of every other configuration on the box that builds it: `pixi run build Debug` on both boxes (the ASan libclang, built with assertions, declares more than the release one), `pixi run build RelWithDebInfo` on macOS, and `pixi run build RelWithDebInfo -- --platforms=@xclang\u002F\u002Fplatforms:\u003Ctriple>` for the cross ones. CI runs them all, but a configuration that does not build is found faster here.\n\n## Step 6: Write the Changelogs (REQUIRED)\n\nToolchain-level findings on clice's side (`MODULE.bazel`, `.bazelrc`, `BUILD.bazel`, `bazel\u002F`, CI mechanics; the toolchain itself keeps its own notes in xclang) go to `toolchain-changelog.md` in this directory, in its symptom \u002F cause \u002F fix \u002F check shape. API changes go to `llvm-changelog.md`, maintainer reference material, deliberately not a docs page.\n\nEvery LLVM upgrade adds a new H2 section to `llvm-changelog.md` (e.g., `## LLVM 22 → 23`) documenting all breaking changes encountered. For each API change, record:\n\n- Change description\n- Upstream commit hash\n- PR number (link to `https:\u002F\u002Fgithub.com\u002Fllvm\u002Fllvm-project\u002Fpull\u002F\u003CNUM>`)\n- Impact on clice\n\nTo find upstream commits, search the LLVM git history between version tags (`git log --oneline llvmorg-\u003COLD>..llvmorg-\u003CNEW> -- clang\u002Finclude\u002Fclang\u002FAST\u002F` in `..\u002Fllvm-project`, or the GitHub history). Group changes by category with a table per category, as the newest section does.\n\n## Step 7: Report and Wait\n\nPresent a summary to the maintainer and **wait for confirmation** before opening the PR. The summary should include:\n\n- All API changes that were adapted and how they were resolved\n- What the regenerated `modules\u002F` dropped, and what `demand.cpp` gained\n- All test expectation changes (snapshot updates, assertion value changes) and why\n- Any unavoidable behavior changes from upstream LLVM (e.g., TypePrinter output differences, type sugar changes) that affect user-visible features like hover\n- The LLVM changelog that was written\n\nThe maintainer decides whether all changes are acceptable or if adjustments are needed.\n\n## Step 8: The PR\n\nThe pr skill takes over; the title is `chore: upgrade LLVM to \u003CX.Y.Z>`.\n\n## Notes\n\n- **Other libraries**: a version bump of kotatsu or any other library `modules\u002F` wraps (its `bazel_dep` in `MODULE.bazel`) is Steps 2 and 4 alone, then the build; so is clice starting to use a header or macro `modules\u002F` does not export yet. A new library is added to `LIBRARIES` in `modules\u002Fmodules.bzl` and to the partition in `scripts\u002Fmodules.py`.\n- **Private headers**: clice includes no private clang headers, and xclang's libclang archives carry none; one clice starts to need goes into xclang's libclang package (`toolchain\u002F` in xclang) first.\n- **Debug builds**: ASan builds (`bazel\u002Fclice.bazelrc`'s Debug) link the ASan libclang, which xclang builds for x86_64 Linux and arm64 macOS (its `@libclang` follows `--features=asan`); the other targets have no Debug build.\n",{"name":5,"description":7},"main","4e1e435a5ef755b61cfc0dd1312d9766781e555b",".claude\u002Fskills\u002Fupgrade-llvm",89,"https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice","https:\u002F\u002Fdocs.clice.io\u002Fclice\u002F","https:\u002F\u002Fgithub.com\u002Fclice-io","https:\u002F\u002Fclice.io\u002F","2026-11-15 03:05:59",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add clice-io\u002Fclice --skill upgrade-llvm",{"tool":54,"command":55},"bunx","bunx skills add clice-io\u002Fclice --skill upgrade-llvm",{"tool":57,"command":58},"pnpm","pnpm dlx skills add clice-io\u002Fclice --skill upgrade-llvm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fupgrade-llvm\u002FSKILL.md",true,[62,68],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"llvm-changelog.md","REFERENCE","参考文档",36425,"https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fupgrade-llvm\u002Fllvm-changelog.md",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"toolchain-changelog.md",10448,"https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fupgrade-llvm\u002Ftoolchain-changelog.md",[73,101,122,141,163,182],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":89,"publishedAt":34},"01M6BZFHCK196E4Z66DGN9QDYJ","write-tests","Read before writing or modifying anything under tests\u002F or unittests\u002F, or the tools' own tests — the case workflow, unit tests, hard rules and known pitfalls.","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwrite-tests\u002FSKILL.md",[79,84],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[90,91,92,93,31,94,95,96,97,98,99,100],"write tests","tests","write","pitfalls","case","unit","unit tests","Tools","workflow","Rules","writing",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":34},"01M6BZFCM31QYASHF2XF6G105C","triage","Use when asked to triage issues — classifies untriaged issues with codex, validates the labels, and returns proposed labels plus an activity digest. Read-only; runs in a forked context.","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriage\u002FSKILL.md",[],[103,108,109,110,111,112,113,114,115,116,31,117,118,119,28,120,121],"issues","returns","only","triage issues","codex","activity digest","context","read-only","activity","digest","fork","with","use","labels",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":34},"01M6BZFAW6TTR0FK91HZ0TVNFS","translate-docs","Read before translating, reviewing or editing any docs\u002Fzh page — clice's glossary and page conventions, on top of the shared translation rules of clice-io\u002Fdocs.","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftranslate-docs\u002FSKILL.md",[],[129,130,131,132,133,134,31,135,136,137,138,139,99,140],"translate docs","translate","docs","zh","io","conventions","top","translation","shared","editing","page","glossary",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":34},"01M6BZF86F54V9BZCW3MJW82VY","test","Run the clice test suites, on a box unless a local run is truly necessary; also how to test on Windows. Optional args = suite (unit | cases | all, default all) build type (Debug | RelWithDebInfo, default RelWithDebInfo) and the box id the build ran on. Runs in a forked context; only a digest returns.","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftest\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000008","测试与质量",[143,151,152,114,153,117,30,118,154,155,110,156,157,95,109,158,159,160,161,162],"local run","local","suite","id","type","how to","default","run","how","debug","box","windows",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":34},"01M6BZF5WRJ6PKYJVW4YKPYD20","resolve-comments","Use in each watch round of an open PR — pulls its unresolved review threads, fixes them in the worktree, resolves them, and returns a compact summary.","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fresolve-comments\u002FSKILL.md",[],[170,171,172,120,173,174,175,109,176,177,178,179,180,181],"comments","resolve comments","open","summary","fixes","threads","review","open pr","worktree","pr","compact","watch",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":34},"01M6BZF3RPE8A4Z9KMJJBJPCPD","release","Read before any release work — instant builds, nightlies, stable tags, publishing, release workflows — or symbolizing a user's crash log.","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease\u002FSKILL.md",[],[184,189,190,191,192,193,31,194,195,196],"log","user","crash","tags","publishing","workflows","instant","work"]