skills.rest
avgarcia
avgarciaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openapi-spec-editor

Manage OpenAPI specification changes before implementation work begins.

Updated May 15, 2026
Search Tags:#frontend#openapi#backend#breaking changes#rest api#contract-first#api contract
One-click install
npx skills add https://github.com/avgarcia/runcriticon --skill openapi-spec-editor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openapi-spec-editor
Source: https://github.com/avgarcia/runcriticon/tree/main/.claude/skills/openapi-spec-editor
Command: npx skills add https://github.com/avgarcia/runcriticon --skill openapi-spec-editor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents API contract drift by enforcing a disciplined contract-first workflow where the OpenAPI specification stays the source of truth before implementation changes begin.

Core Features & Use Cases

  • Contract-first API updates: Guides endpoint, schema, parameter, and status code changes through spec editing before backend or frontend work.
  • Breaking change control: Helps classify additive versus breaking API changes and applies the required review and migration discipline.
  • Implementation alignment: Coordinates client regeneration, backend and frontend updates, contract testing, and cross-team review for monorepo API changes.

Quick Start

Use the openapi-spec-editor skill to add or modify an API endpoint while following the Runcriticon contract-first workflow.

Frequently Asked Questions about openapi-spec-editor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent breaking changes when updating a REST API contract?▼

To prevent breaking changes in a REST API contract, you must classify modifications as additive or breaking before implementation. This ensures required reviews and migration steps are applied to maintain backward compatibility.

What is contract-first API evolution and how does it manage OpenAPI specifications?▼

Contract-first API evolution uses OpenAPI specifications as the single source of truth before implementation begins. It manages endpoint and schema updates through disciplined spec editing, ensuring backend and frontend alignment.

How do I coordinate client regeneration and contract testing for monorepo API changes?▼

Coordinate client regeneration and contract testing by aligning backend and frontend updates through cross-team reviews. This workflow ensures implementation matches the updated API contract across all affected services.

Can I use this approach to guide endpoint additions and schema updates before backend work?▼

Yes, you can guide endpoint additions, schema updates, and status code changes by editing the OpenAPI specification first. This workflow enforces cross-team review and implementation alignment before backend work starts.

When do I need to classify additive versus breaking OpenAPI specification changes?▼

You need to classify additive versus breaking OpenAPI specification changes whenever modifying endpoints or schemas. This classification determines the required migration discipline and cross-team review practices for safe API compatibility.

Related Skills

Explore More Software Engineering Skills→
azmankudusazmankudus

blueprint-webapi

Enforce API contracts using a single OpenAPI 3.1 master specification.

Community
Advanced
askaretaskaret

fullstack-slice

Automate coordinated .NET backend and React frontend changes with contract-first updates.

Community
Intermediate
heaptracetechnologyheaptracetechnology
13

contract-test

Automate API contract testing with schema validation and OpenAPI checks.

Community
Advanced
ccfccf

openapi-spec-generation

Generate and validate OpenAPI 3.1 specifications from design or code sources.

Community
Advanced