api-changes Skill
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-chec Published by microsoft in FluidFramework.
Decision snapshot
Is this a fit?
Developers using FluidFramework, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is api-changes Skill?
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-chec Published by microsoft in FluidFramework. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using FluidFramework
Declared skill metadata
- Source file: .claude/skills/api-changes/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use api-changes Skill
- Use it for developers using fluidframework.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/FluidFramework
- Skill file: .claude/skills/api-changes/SKILL.md
What it does
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-chec
Skill instructions
<required Before doing any work, create one task/todo item per applicable step using your available task tooling (TaskCreate for Claude, TodoWrite for Copilot). Mark each task inprogress when you start it and completed when you finish. This prevents steps from being silently skipped as context grows. </required API Changes Review Step 1: Identify what changed Read .claude/skills/comparison-base/SKILL.md and execute it with HEAD as $REVIEWREF. 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: bash git diff "$BASECOMMIT" -- ':(glob)/api-report/.md' git ls-files --others --exclude-standard -- ':(glob)/api-report/.md' 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 stage
Verified compatibility and discovery
Frequently asked questions
What is api-changes?
api-changes is a open-source AI agent skill with Copy skill directory. Use when customer-facing API changes were made — i.e., API report .md files differ from the branch's resolved comparison base.
Who is api-changes best for?
api-changes is best for reusing agent instructions, scripts, and references.
How do I install api-changes?
Install or run api-changes using Copy skill directory. Check api-changes for the latest setup command.
Is api-changes actively maintained?
api-changes may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
