$ ~/registry/skill/microsoft-claude-skills-fluid-pr

SKILL

fluid-pr

Name: fluid-pr
Author: microsoft

为 Fluid Framework 仓库自动生成规范 PR 标题与描述，并推送分支创建拉取请求

星标

★ 4,934

来源

GitHub

更新于

2026-07-19

// 安全评估需留意

仅提示词，不执行代码
开源可审计

总评

该技能属于开源的提示型 PR 工作流说明，本身未声明需要密钥或固定远程端点，整体风险较低。需注意其文档明确包含 git push 与 gh pr create 等操作指引，若宿主代理具备相应工具能力，则会涉及代码托管平台交互与仓库写操作，应在用户确认和最小权限前提下使用。

凭证密钥低风险

材料未声明需要 API key、token 或环境变量；技能文本本身不要求用户提供凭证。潜在认证仅可能来自宿主环境已登录的 git/GitHub CLI，但这不属于该技能额外索取凭证。

网络外发需留意

文档指向推送分支并创建 GitHub PR，存在将分支与 PR 内容发送到代码托管平台的常规外发行为；虽未声明固定 host，但目标与功能相关且可预期，不见无关或不明端点。

代码执行需留意

README 明确包含执行 git remote get-url、git push、gh pr create、以及写临时文件等命令/操作指引，说明若由具备工具能力的代理运行，将涉及本机命令执行与仓库写操作。这属于该类工具的常规能力，材料中未见要求更高系统权限的红旗。

数据访问需留意

为生成与创建 PR，技能会接触当前仓库分支状态、remote 配置以及拟提交的标题/正文，并可能写入临时文件保存 PR 内容；访问范围与声明用途基本一致，未见要求广泛读取无关本地数据。

来源供应链低风险

系统检查项表明其为 prompt-only 且 open-source；来源指向 GitHub 上的微软相关开源仓库，源码可审计，这些均显著降低供应链风险。需留意提供的仓库链接似为总项目仓库而非该具体技能的独立发布单元，且 star/维护信息有限，建议结合实际提交历史复核。

安全建议

仅在确认当前仓库、目标 remote 与分支正确后使用，并保留用户显式确认再执行 push/建 PR。
为宿主代理限制仓库与命令权限，避免该流程可访问无关目录或执行额外命令。
若环境已登录 GitHub CLI 或 git 凭证，优先使用最小权限账号，并确认不会向上游主仓库直接推送。
审查所加载的关联技能（如 fluid-pr-guide）内容，避免间接引入未审核提示或模板。

审计模型: gpt-5.4 · 2026-06-17

// 安装

复制安装指令，让 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. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

创建功能修改的 PR

输入

请为 Fluid Framework 仓库创建一个 PR。根据当前分支改动生成符合规范的 PR 标题和描述，先展示给我确认，然后推送分支并在 GitHub 上创建 PR。

预期产出

先给出符合仓库规范的 PR 标题和正文草稿，确认后完成分支推送并返回 PR 链接。

修复 Bug 后提交 PR

输入

我刚修复了一个 Fluid Framework 的 bug，帮我提交 PR。请根据提交内容整理清晰的标题、摘要和测试说明，并创建 GitHub PR。

预期产出

输出一份结构清晰的 PR 内容，涵盖变更说明与测试信息，并完成 PR 创建。

推送分支并发起 PR

输入

把当前分支推送到远程并创建 PR。请按 Fluid Framework 约定编写标题和正文，如果内容不完整先提示我补充。

预期产出

生成规范化 PR 文案，必要时向用户补充询问，然后完成推送与 PR 发起流程。

// 文档

<required> *CRITICAL* Do NOT run `gh pr create` until the user has explicitly confirmed via AskUserQuestion in step 5. Do not skip ahead.

CRITICAL Add the following steps to your task/todo list using your available task tooling (TaskCreate for Claude, TodoWrite for Copilot):

Confirm you are NOT on 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.
Verify that the 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.
Load the 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.
Using the loaded fluid-pr-guide, compose the PR title and body following its conventions and template.
Print the proposed title and body as text, then immediately use the AskUserQuestion tool to let the user choose what to do next. Use these exact options:
- "Create PR" — Push the branch and open the pull request
- "Create draft PR" — Push the branch and open a draft pull request
- "Edit" — Revise the title or body before creating
- "Cancel" — Don't create a PR
If the user picks "Edit", apply their edits and re-present (go back to step 5). If "Create PR" or "Create draft PR", push and create accordingly. If "Cancel", stop. </required>

Pushing and Creating the PR

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.

Updating an existing PR description

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."

帮助团队执行 Fluid 客户端版本发布流程，涵盖分支、升版、变更日志与发布说明。

microsoft装→

$ loading_

请帮我安装 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. 装好后重载技能，告诉我可以用了

// 用法示例

创建功能修改的 PR

输入

请为 Fluid Framework 仓库创建一个 PR。根据当前分支改动生成符合规范的 PR 标题和描述，先展示给我确认，然后推送分支并在 GitHub 上创建 PR。

预期产出

先给出符合仓库规范的 PR 标题和正文草稿，确认后完成分支推送并返回 PR 链接。

修复 Bug 后提交 PR

输入

我刚修复了一个 Fluid Framework 的 bug，帮我提交 PR。请根据提交内容整理清晰的标题、摘要和测试说明，并创建 GitHub PR。

预期产出

输出一份结构清晰的 PR 内容，涵盖变更说明与测试信息，并完成 PR 创建。

推送分支并发起 PR

输入

把当前分支推送到远程并创建 PR。请按 Fluid Framework 约定编写标题和正文，如果内容不完整先提示我补充。

预期产出

生成规范化 PR 文案，必要时向用户补充询问，然后完成推送与 PR 发起流程。

// 文档

<required> *CRITICAL* Do NOT run `gh pr create` until the user has explicitly confirmed via AskUserQuestion in step 5. Do not skip ahead.

CRITICAL Add the following steps to your task/todo list using your available task tooling (TaskCreate for Claude, TodoWrite for Copilot):

Confirm you are NOT on 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.
Verify that the 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.
Load the 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.
Using the loaded fluid-pr-guide, compose the PR title and body following its conventions and template.
Print the proposed title and body as text, then immediately use the AskUserQuestion tool to let the user choose what to do next. Use these exact options:
- "Create PR" — Push the branch and open the pull request
- "Create draft PR" — Push the branch and open a draft pull request
- "Edit" — Revise the title or body before creating
- "Cancel" — Don't create a PR
If the user picks "Edit", apply their edits and re-present (go back to step 5). If "Create PR" or "Create draft PR", push and create accordingly. If "Cancel", stop. </required>

Pushing and Creating the PR

Before pushing, verify that origin does not point to microsoft/FluidFramework. Run:

git remote get-url origin

# 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.

Updating an existing PR description

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."