$ loading_
在推送代码或触发 CI 前检查常见问题，提前发现格式、变更集与策略风险。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "ci-readiness-check" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/FluidFramework/main/.claude/skills/ci-readiness-check/SKILL.md 2. 保存为 ~/.claude/skills/ci-readiness-check/SKILL.md 3. 装好后重载技能，告诉我可以用了
请帮我做一次 ci readiness check，确认这个分支在推送前没有常见 CI 问题。
返回一份推送前检查结果，指出格式、API 报告、changeset 或策略相关的问题及修复建议。
我准备 push 这个分支了，先检查一下是否 ready for CI，并列出需要我先处理的问题。
输出分支是否适合推送的结论，并给出按优先级排序的待修复项。
请做一个 pre-push check，重点看看有没有漏掉 changeset、格式化或违反仓库策略的地方。
给出遗漏项清单，并说明哪些问题会导致 CI 失败或阻止合并。
There are exactly two narrow exceptions where you MAY skip the Step 1 mode-choice question. Both must be applied conservatively; if you are not certain an exception applies, you MUST ask.
.claude/, repo-root README.md / CHANGELOG.md, top-level docs not in a docs/* package). Watch out: docs/api/ and similar are themselves workspace packages — markdown inside a workspace package does NOT automatically qualify. If you cannot quickly verify the changed files are outside every workspace package, ask.If either exception applies, treat it as equivalent to the user picking Skip in Step 1: do NOT ask the mode-choice question, do NOT create CI-readiness tasks/todos, and do NOT run the CI script or any other build/test/API-report steps. Stop the skill after reporting the skip.
When you apply an exception, you MUST explicitly report — every single time, with no abbreviation across repeated runs — that (a) you skipped asking the mode-choice question, (b) the CI readiness check itself was skipped, and (c) which exception applied. Silent skipping is forbidden.
When neither exception applies, ask the user and wait for their response. Immediately after they respond, create one task/todo item per applicable step using your available task tooling (TaskCreate for Claude, TodoWrite for Copilot) — before doing any other work. Mark each task in_progress when you start it and completed when you finish. This prevents steps from being silently skipped as context grows.
Tasks to create by mode:
For Build/Test: if @fluidframework/tree is among the changed packages and its API surface likely changed, add a "Cascade API reports to aggregator packages" task after "Regenerate API reports".
Omit steps that don't apply (e.g. skip "Build unbuilt packages" if everything is already built; skip "Regenerate API reports" and "Regenerate type tests" if the API surface didn't change). </required>
Before doing anything, ask the user:
I can run a CI readiness check on your branch. Pick a mode (fastest to slowest):
- Skip — skip the CI readiness check
- Check (quick) — auto-fix formatting, policy, and syncpack on changed packages
- Build — Check + build unbuilt packages + ESLint + regenerate API reports and type tests
- Test (slower) — Build + run the test suite in changed packages
Wait for the user's response. If they say skip (or anything clearly negative), stop here. Otherwise, note their choice and immediately create tasks for all remaining steps as described in the required block above before proceeding.
Run the bundled script from the repository root:
bash .claude/skills/ci-readiness-check/ci-readiness-check.sh [base-branch]
…
帮助你严谨评估代码评审意见，澄清疑点后再决定是否采纳与实现
对本地或PR分支执行结构化代码审查，帮助提交或发布前发现问题。