Detect breaking changes in docs/mapi/openapi.yaml and check whether the committed spec is stale; run the OAS checks, interpret findings, and guide fixes.
82
72%
Does it follow best practices?
Impact
100%
1.56xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/agent-standards/skills/check-oas/SKILL.mdOAS breaking-change detection script
Read version from file
0%
100%
GitHub release URL
100%
100%
Linux amd64 tar.gz
100%
100%
oasdiff breaking subcommand
100%
100%
Error vs warning distinction
100%
100%
Exit 1 on errors (no exemption)
100%
100%
Prints findings even if exempted
100%
100%
Minor version bump exemption
100%
100%
Patch-zero exemption
100%
100%
Actual output captured
100%
100%
Breaking change remediation guide from CI output
Errors cause failure
100%
100%
Warnings are non-blocking
100%
100%
Fix: keep removed response field
100%
100%
Fix: deprecate removed response field
100%
100%
Fix: keep removed enum value
100%
100%
Fix: deprecate before removing operation
100%
100%
Fix: remove in new minor version
0%
100%
Fix: make new param optional
100%
100%
Warnings identified correctly
100%
100%
All 6 findings addressed
100%
100%
OAS maintenance workflow runbook for new developers
Staleness exit codes
20%
100%
--also-make flag
0%
100%
First-run baseline note
0%
100%
Regeneration command
20%
100%
Commit spec with code
100%
100%
Baseline: master/release branches
0%
100%
Baseline: other branches
0%
100%
Minor version bump exemption
0%
100%
Patch-zero exemption
0%
100%
--use-head false flag
0%
100%
9821842
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.