fluid-pr
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".
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 4.9k
- Forks
- 590
01 前言 Front Matter
- name
- fluid-pr
- license
- MIT
- description
- 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".
03 SKILL.md 正文
<required>
CRITICAL Do NOT run gh pr create until the user has explicitly confirmed via the ask_user tool in step 5. Do not skip ahead.
CRITICAL Add the following steps to your task/todo list using the available Copilot task-management tooling:
- Confirm you are NOT on
mainor 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
originremote does not point tomicrosoft/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. Pipeline changes on branches prefixed withtest/are an exception. - Load the
fluid-pr-guideskill 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
ask_usertool 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 unless the branch is prefixed with test/ and the conversation context or changed files indicate that the change needs Azure Pipelines testing. A user request for a "test branch" in that context is sufficient intent to use the exception. Otherwise, tell the user they should push to their fork instead and do not proceed.
Once the checks in steps 1–2 pass silently, compose the title and body, print them as text, then use the ask_user 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
When asked to update an existing PR's title or body, use gh pr edit to apply the changes directly.
Specify --repo <owner/repo> to avoid ambiguity between forks and upstream.
For a description update, write the new body to a temp file, then apply it to the PR:
cat <<'EOF' > "$TMPDIR/pr-body.md"
<new body content>
EOF
gh pr edit <number> --repo <owner/repo> --body-file "$TMPDIR/pr-body.md"
To update the title, use gh pr edit <number> --repo <owner/repo> --title "<new title>". After updating, output the PR URL.
04 同仓库更多 Skills
trigger-pipelines-for-copilot-pr
Trigger ADO pipelines for a Copilot-created PR by posting /azp run comments. Use when the user asks to trigger CI pipelines for a specific PR.
review
Review changes relative to a prior state, such as a diff, pull request, branch, commit, or working-tree changes. Use for change-focused code review and regression analysis. Do not use to assess an existing file, API, design, implementation, or other artifact without a comparison; if the request is ambiguous, ask whether the user wants a change review and what prior state to compare against.
review-pr-local
The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored review prose the human did not ask for, invoke this skill instead.
policy-check
This skill should be used when the user asks to "run policy check", "check policy", "policy-check", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.
pipeline-test-triage
Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this pipeline fail", "summarize the test failures", "is this test flaky or a real bug", "compare these runs", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.
fluid-release
Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on "release", "do the release", "release status", version bump, release notes, changelog, release branch, or release engineering.