Repository navigation
docs(skills): no JSON Schema detection for AsyncAPI/Arazzo roots - #11115
Closed
RobertHebel wants to merge 1 commit into
Closed
RobertHebel wants to merge 1 commit into
RobertHebel wants to merge 1 commit into
Conversation
A document is a standalone JSON Schema document only when its root has the dialect's $schema and none of the API description fields openapi, swagger, asyncapi and arazzo. This was answered as PRD decision D18 on 2026-10-27 and matches swagger-client's isJSONSchema202012 predicate. It becomes decision 8 of /add-json-schema-support: SKILL.md (the description, Step 1 and the Step 4 detection and test items), references/dialects.md (the detection rule) and references/design-and-delivery.md. design-and-delivery.md also maps the skill decisions to the "Standalone JSON Schema 2020-12" PRD numbers (D1-D19) and records the PRD decisions that bound every dialect: D3 (no cross-dialect $refs), D5 ($dynamicRef left in place), D6 (bundling deferred), D12 (allOf merging as for OAS 3.1) and D13 (start on upstream tarballs, merge after the swagger-client release). Skill decision 2 stays open. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Superseded: recreated with commits cherry-picked onto latest main. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Records decision D18 of the "Standalone JSON Schema 2020-12" PRD as decision 8 of
/add-json-schema-support: a document is a standalone JSON Schema document only when its root has the dialect's$schemaand none ofopenapi,swagger,asyncapi,arazzo. This matches swagger-client'sisJSONSchema202012.SKILL.md(description, Step 1, Step 4 detection and test items) andreferences/dialects.md.references/design-and-delivery.mdalso maps the skill decisions to the PRD's D-numbers and records D3, D5, D6, D12 and D13. Decision 2 (later drafts) stays open.Motivation and Context
The skill said "no
openapi/swaggerfield". AsyncAPI and Arazzo documents can carry a root$schematoo, and the swagger-client strategy already refuses them.How Has This Been Tested?
bash .claude/skills/add-oas-support/scripts/test/smoke.sh(53 ok) andverify-urls.mjson the changed files (0 broken).Checklist
src/is unmodified)🤖 Generated with Claude Code