OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add microsoft/fluidframework --skill api-changes
Use when customer-facing API changes were made — i.e., API report .md files differ from the branch's resolved comparison base. 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.
npx skills add microsoft/fluidframework --skill api-changes
Read .claude/skills/comparison-base/SKILL.md and execute it with HEAD as $REVIEW_REF. This is required; use the target and comparison commit it resolves.
Compare the selected base with the working tree, not just HEAD, because this skill is often called immediately after API reports have been regenerated and those edits may be uncommitted:
Treat the union of both command outputs as the changed API reports. For each untracked report, read the full file as a new API surface because it has no Git diff until staged.
Build a summary table and present it to the user:
| Package | Change type | Tag(s) | Breaking? |
|---|
Change types: addition, removal, signature change, tag promotion.
If all changes are @internal-only, tell the user there are no customer-facing API changes and stop.
For any new exports, verify each has a release tag and flag any missing ones to the user — API Extractor will fail with ae-missing-release-tag. Help the user choose the right tag:
| Tag | When to use |
|---|---|
@public | Stable, production-ready. Full SemVer. Use only when the shape is final. |
@beta | Seeking feedback, path to @public. Production OK with caution. |
@alpha | Experimental, early feedback only. Not for production. No stability guarantees. |
@internal | Framework-internal only, not for external consumers. |
When in doubt: @alpha — easier to promote than demote. @legacy is a paired modifier (@legacy @public or @legacy @alpha) for FF v1 APIs; don't apply it to new APIs.
For every new customer-facing export (@public, @beta, @alpha) that is intended to be usable by package consumers, verify it is reachable from the package's public entrypoint, not just exported from the adjacent module or folder. Trace and update the export chain through every relevant index.ts barrel up to the package root entrypoint (typically src/index.ts, or tiered entrypoints such as src/alpha.ts / src/beta.ts where used). Missing parent-barrel exports are incomplete API changes. API Extractor may not report the intended API at all, and consumers are expected to import from the package's top-level entrypoint rather than reaching into subpaths.
Also check that each new customer-facing export (@public, @beta, @alpha) has TSDoc documentation — at minimum a summary, @param tags, and @returns if applicable. Flag any missing documentation to the user.
Tell the user whether their change requires API Council approval:
| Changed surface | Approval required? |
|---|---|
@public, @legacy @public, @beta, @legacy @alpha | Yes — fluid-cr-api will be automatically assigned as a required reviewer on the PR |
@alpha only (not @legacy) | No — but early engagement with the council is encouraged |
@internal only | No |
Tell the user: council approval is a separate sign-off from the area owner review. To engage the council, they can reach out to the API Council member on their EM team or tag @FF API on Teams. Share this link with the user for more details:
https://eng.ms/docs/experiences-devices/opg/office-shared/fluid-framework/fluid-framework-internal/fluid-framework/docs/dev/resources/api-council
A breaking change removes or modifies an existing API in a way that causes compile errors for consumers upgrading.
If this is a breaking change to @public or @legacy @public, tell the user this is likely a mistake — major releases happen very rarely. Breaking @public APIs must be coordinated with a major release; the old API must be deprecated at least 3 months prior in a minor release with a clear replacement.
Share these links with the user for the required process:
If this is a breaking change to @beta or @legacy @alpha, tell the user:
test/breaks/client/#.#0/ branch and held until the break window opensShare these links with the user:
Tell the user: while @alpha has no contractual stability guarantees, there is an informal agreement not to break office-bohemia. If this change could break office-bohemia, it should be staged using the same process as above.
Also tell the user: if they skip this check and the change does break office-bohemia, the daily integration pipeline will catch it and FF OCE will revert the PR or contact them to do so ASAP.
If any API is being deprecated, check that the following are in place and flag anything missing to the user:
@deprecated TSDoc comment includes: version deprecated, version of removal, replacement, and a link to the tracking issue:
Share this link with the user for full deprecation guidance: ../../../docs/content/Contributing/API-Deprecation.md
All customer-facing API changes require a changeset — additions, modifications, deprecations, tag promotions, removals.
Check whether one exists: git status --porcelain -- .changeset/
If none exists, create one on behalf of the user from the repo root:
This drops a randomly-named file in .changeset/. Edit it with content based on what changed. YAML front matter lists affected packages (only those meaningful to consumers) with bump type minor, plus "__section" to route to the right release notes section: feature (new APIs), deprecation, breaking (major / server only; use legacy for legacy API breaks), tree (changes to SharedTree/@fluidframework/tree APIs), fix, or other.
Summary line rules (from .changeset/README.md): succinct, no terminal punctuation, no backtick formatting, present tense. Prefix test: mentally prepend "In this release," to verify it reads naturally. Body may include a code example for features, deprecations, and breaking changes.
After drafting the changeset, show the content to the user and confirm it looks right before moving on.
Present the user with a clear summary:
End with a clear go/no-go: "Your changes look good to merge" or "Please resolve these issues before merging: …"