fluid-pr-guide
Use when composing, writing, drafting, or reviewing a PR title, PR description, or PR body in Fluid Framework — provides title style, body template, and section guidance.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 4.9k
- Forks
- 590
01 前言 Front Matter
- name
- fluid-pr-guide
- license
- MIT
- description
- Use when composing, writing, drafting, or reviewing a PR title, PR description, or PR body in Fluid Framework — provides title style, body template, and section guidance.
03 SKILL.md 正文
Use Option A for build-tools PRs because this group generates changelogs from commits. For other PRs, use either style unless the package documents a different requirement. Do not mix the two styles.
Option A — Conventional Commits prefix:
type(optional-scope): short imperative description
- Common types:
fix,feat,chore,build,docs - Scope is a package or area name (e.g.,
build-cli,id-compressor,eslint-config-fluid) - Examples:
fix: Prompt copilot-oce to check for Teams channel repliesfix(build-cli): remove flaky parallel changeset testfeat(devcontainer): add agency installation and update host requirementschore: move misplaced @types/ packages from dependencies to devDependenciesbuild(client): Update type tests after minor release 2.91.0
Option B — Plain imperative:
Short imperative or noun-phrase description
- No prefix, just a clear description of what changed
- Examples:
Port MessageCodec to ClientVersionDispatchingCodecBuilderRemove tree checkout's branch methodEnsure a summarizer stop request is respected after connecting
Never use the [bump] prefix — that is reserved for automated bot PRs.
Always include a ## Description section, even if it is brief and somewhat redundant with the title.
PR Body Template
Read .github/pull_request_template.md from the repo root and use it as the starting point for the PR body. Fill in each relevant section, then delete sections and placeholder text that don't apply — do not leave empty sections.
CI requirement: the preamble line "Feel free to remove or alter parts of this template..." must be removed from the PR body. Leaving it in will cause the
.github/workflows/pr-validation.ymlcheck to fail.
Notes on body sections
## Description: Focus on why and impact, not just what lines changed. For bug fixes, include repro steps or a test that demonstrates the fix.## Breaking Changes: Only include when a change removes or alters public API surface or behavior in a way that requires consumer action (like migration or build-time updates). Link the wiki page.## Reviewer Guidance: Always include the wiki link line. Add content if you have specific asks; delete the placeholder bullets if you don't. If design questions are unresolved, mark the PR as a draft.- Azure DevOps work items: Reference inline in the body as
AB#<item-id>if applicable (e.g.AB#12345). No dedicated section needed.
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.