菜单
Diagnose a spurious stage1 test failure caused by olean-persisted compiler changes. Use when a stage1 test fails unexpectedly and the change adds or modifies an environment extension or other information persisted into .olean files.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/leanprover/lean4 --skill stage2-olean-test命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Retrieve and investigate failing Lean CI job logs. Use when a CI job fails and you need to fetch its logs, or when monitoring a CI run for failures.
Build and run tests against the stage2 Lean compiler. Use when asked to build, rebuild, or test against stage2.
Write the Highlights section for Lean 4 release notes. Use when asked to write, draft, or update release highlights for a Lean version.
基于 SOC 职业分类
| name | stage2-olean-test |
| description | Diagnose a spurious stage1 test failure caused by olean-persisted compiler changes. Use when a stage1 test fails unexpectedly and the change adds or modifies an environment extension or other information persisted into .olean files. |
| allowed-tools | Bash, Read |
When a change alters information that is persisted into .olean files (e.g. a new or changed
environment extension that the compiler reads back), a stage1 test run can fail spuriously: stage1's
src/ (including Init) is compiled by the stage0 compiler, which lacks the change, so the
stage1 lean binary imports oleans that predate the change. In that situation the relevant tests
must be run against stage2 instead, where the new compiler compiles everything consistently.
So: on a test failure, if the change depends on changed olean information, test stage2 instead.
Building stage2 is expensive, so confirm with the user before switching to a stage2 build.
For the actual build/test commands (make stage2, clean-stdlib, per-module Lake builds, and
running tests against stage2), use the stage2-build skill.
