Answer: The OpenAPI specification prompt analyzes API endpoint code and generates a valid OpenAPI 3.0 specification in YAML format, producing a production-ready spec usable with Swagger UI, Postman, and code generators. Status: Confirmed Entry: tool/github-copilot/features/openapi-specification-prompt Revision: 3 Digest: sha256:c2a593b3e5ad5eb9 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:34:13Z Last changed: 2026-11-19T13:10:12Z (compatibility: — → Swagger UI, Postman, and code generators) Last verified: 2026-11-20T13:16:32Z Next check: 2026-11-21T13:16:32Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of task | Analyze the API endpoint code and generate a valid OpenAPI 3.0 specification in YAML format | [1] | 2026-11-20 OpenAPI version | 3.0.3 | [1] | 2026-11-20 output format | YAML | [1] | 2026-11-20 compatibility | Swagger UI, Postman, and code generators | [1] | 2026-11-20 description | Generate OpenAPI 3.0 specification for API endpoints | [1] | 2026-11-20 Sources: [1] GitHub. "Document API - GitHub Docs". https://docs.github.com/en/copilot/tutorials/customization-library/prompt-files/document-api Role: primary. Accessed: 2026-11-20T13:16:32Z Quote: "Analyze the API endpoint code and generate a valid OpenAPI 3.0 specification in YAML format." (Supports: task) Quote: "OpenAPI version (3.0.3)" (Supports: OpenAPI version) Quote: "generate a valid OpenAPI 3.0 specification in YAML format" (Supports: output format) Quote: "Generate production-ready OpenAPI specification that can be used with Swagger UI, Postman, and code generators." (Supports: compatibility) Quote: "description: 'Generate OpenAPI 3.0 specification for API endpoints'" (Supports: description) Snapshot SHA-256: 31d1e7953d9263ef5561126c83336bc7dfb5c9c75830c7bb7a40b3e6ee48fd88 (captured 2026-11-18T13:13:13Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T13:13:13Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:16:32Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:16:32Z Last attempt: 2026-11-20T13:16:32Z Notes and limitations: Extracted automatically from a single official source (section "OpenAPI specification prompt"). Related: https://latestn.com/tool/github-copilot/features/plugin-contents What do GitHub Copilot plugins contain? https://latestn.com/tool/github-copilot/features/plugin-folder-layout What folder layout does a GitHub Copilot plugin directory require? https://latestn.com/tool/github-copilot/features/plugin-formats What plugin formats does GitHub Copilot support? https://latestn.com/tool/github-copilot/features/mcp-best-practices What are the best practices for using MCP with GitHub Copilot agent mode? https://latestn.com/tool/github-copilot/features/mock-objects-example-prompt What example prompt can I give GitHub Copilot to generate mock objects? https://latestn.com/tool/github-copilot/features/onboarding-plan-prompt-contents What does the GitHub Copilot onboarding plan prompt contain? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:10:12Z | changed | compatibility: — → Swagger UI, Postman, and code generators | [1] 2026-11-19T13:10:12Z | changed | compatible tools: Swagger UI, Postman, and code generators → — | [1] 2026-11-17T13:36:54Z | changed | task: Analyze the API endpoint code and generate a valid OpenAPI 3.0 specification in YAML format. → Analyze the API endpoint code and generate a valid OpenAPI 3.0 specification in YAML format | [1] 2026-11-13T03:34:13Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/features/openapi-specification-prompt/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/features/openapi-specification-prompt POST: https://latestn.com/dispute/tool/github-copilot/features/openapi-specification-prompt with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/features/openapi-specification-prompt?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What does the OpenAPI specification prompt in GitHub Copilot do? Revision 3, last verified 2026-11-20T13:16:32Z. https://latestn.com/tool/github-copilot/features/openapi-specification-prompt (accessed 2026-11-21T09:52:29Z). @misc{LatestN_tool_github_copilot_features_openapi_specification_prompt_r3, title = {What does the OpenAPI specification prompt in GitHub Copilot do?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/features/openapi-specification-prompt}}, note = {Revision 3; digest sha256:c2a593b3e5ad5eb9; last verified 2026-11-20T13:16:32Z; accessed 2026-11-21T09:52:29Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/features/openapi-specification-prompt