$ loading_
Use when creating a pull request in the Fluid Framework repo. Composes a PR title and body following Fluid Framework conventions, proposes them to the user, then pushes the branch and creates the PR on GitHub. Triggers on "create a PR", "make a PR", "open a PR", "submit a PR", or "push and create a PR".
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "fluid-pr" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/FluidFramework/main/.claude/skills/fluid-pr/SKILL.md 2. 保存为 ~/.claude/skills/fluid-pr/SKILL.md 3. 装好后重载技能，告诉我可以用了
CRITICAL Add the following steps to your task/todo list using your available task tooling (TaskCreate for Claude, TodoWrite for Copilot):
main or any release branch. If you are, stop and tell the user: you cannot create a PR from a protected branch — they need to create or switch to a feature branch first.origin remote does not point to microsoft/FluidFramework. If it does, stop and tell the user: pushing a branch directly to the main repo is not allowed — they should push to their fork instead.fluid-pr-guide skill NOW (via the Skill tool) before composing anything. It contains the title conventions, body template, and section guidance you need. Do NOT skip this step or rely on memory.fluid-pr-guide, compose the PR title and body following its conventions and template.AskUserQuestion tool to let the user choose what to do next. Use these exact options:
Before pushing, verify that origin does not point to microsoft/FluidFramework. Run:
git remote get-url origin
If the URL contains microsoft/FluidFramework, stop — pushing a branch directly to the main repo is almost certainly not intended. Tell the user they likely need to push to their fork instead. Do not proceed.
Once the checks in steps 1–2 pass silently, compose the title and body, print them as text, then use the AskUserQuestion tool with the four options as described in step 5. This is the only point where the fluid-pr flow asks the user a question.
# Push branch (first time)
git push -u origin <feature-branch>
# Create PR (option 1)
gh pr create \
--title "<title>" \
--body "$(cat <<'EOF'
<body>
EOF
)"
# Create draft PR (option 2) — add the --draft flag
gh pr create \
--draft \
--title "<title>" \
--body "$(cat <<'EOF'
<body>
EOF
)"
After creating the PR, output the PR URL so the user can navigate to it.
You do not have permissions to edit PRs on the upstream microsoft/FluidFramework repo via the API. If you need to update an existing PR's title or body, write the new content to a temp file and tell the user to copy-paste it into GitHub:
cat <<'EOF' > "$TMPDIR/pr-body.md"
<new body content>
EOF
Then tell the user: "I can't edit the PR directly — I've written the updated description to $TMPDIR/pr-body.md. Please copy-paste it into the PR on GitHub."
Use this skill for any Kusto query or telemetry investigation specifically related to Fluid Framework or its partners. Triggers include: writing or running a Kusto query against the Office Fluid database, investigating Fluid Framework telemetry or error rates, querying Office_Fluid_FluidRuntime_* tables, looking up a Fluid session by Session_Id or docId, investigating a Fluid-related error in Loop or Whiteboard telemetry, monitoring an FF bump or partner ring deployment, checking Fluid render reliability or Scriptor errors, or when the user mentions Fluid-specific tables (Office_Fluid_FluidRuntime_*, OwhLoads, HostTracker, Scriptor) or Fluid-specific error types (dataCorruptionError, dataProcessingError, DeltaConnectionFailureToConnect, ICE, ACE). Do NOT trigger for general Kusto questions that are not related to Fluid Framework.
IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration
Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.
Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts
Generate the OCE shift status dashboard. Triggers on: 'generate shift dashboard', 'show dashboard', 'shift status', 'status dashboard', 'what's going on', or any request for a NON-SPECIFIC overview of current OCE status (incidents, pipelines, errors).