Обновление зависимости LLVM в проекте

★ 7.0 · devops

Upgrade LLVM Version in Project is a Claude Code skill that guides a developer through the full cycle of upgrading prebuilt LLVM packages in the clice project — from triggering a CI build to pinning the version in cmake and writing a structured changelog. Reach for it when a new LLVM release is out and you need to bump the dependency in clice, when compilation breaks after a version change due to API breakage, when CI fails on stale manifest hashes, or when breaking changes need to be documented for the team. The skill covers 8 ordered steps: triggering the `build-llvm` GitHub Actions workflow (polling ~2–3 h across 14 matrix builds), downloading the local-platform artifact, adapting API changes (headers, namespaces, type system, function signatures), opening a PR, running `release-llvm` with unused-library pruning, updating `setup_llvm("<VERSION>")` in `cmake/package.cmake`, appending a categorised changelog to `llvm-changelog.md`, and presenting a summary to the user before the final push — confirmation is required. Stack: pixi, CMake, gh CLI, bash. This goes in one direction — upgrading LLVM upward — not setting up LLVM from scratch in an arbitrary project.