api-changes Skill
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 detec Published by microsoft in FluidFramework.
What is api-changes Skill?
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 detec 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.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use api-changes Skill
- Use it for documentation.
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 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 detec
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 bash git diff $(git merge-base HEAD origin/main)...HEAD -- '/api-report//.md' 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. --- Step 2: Check release tags, documentation, and export reachability 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:
Explore related resources
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 main.
Who is api-changes best for?
api-changes is best for reusing agent instructions, scripts, and references, documentation workflows.
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.
Auto-fetched from GitHub.
