fluid-pr-guide
There is no enforced title policy in this repo. Two styles appear in roughly equal proportion — use whichever fits the change. Do not mix them (e.g., don't add a fix: prefix to an otherwise plain-imperative title just because it's a bug fix).
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:
More from microsoft/fluidframework
review
Use when asked to review code, review a branch, or do a code review. Spawns Breaker (correctness) and API Analyst (compatibility/conventions) sub-agents while the orchestrator reviews architecture, tests, performance, and security.
3fluid-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".
2api-changes
Use when customer-facing API changes were made — i.e., API report .md files differ from main. Guides through release tag assignment, API Council review requirements, breaking change classification, deprecation process, and changeset guidance. Triggered automatically by ci-readiness-check when api-report diffs are detected.
2ci-readiness-check
Use when the user explicitly asks for a CI check or to push their branch — e.g. "ci readiness", "check ci", "pre-push check", "ready for CI", "ci check", "ready to push", "push my changes", "push the branch", "let's push". Catches common CI failures before pushing — formatting, stale API reports, missing changesets, policy violations.
2