Generate and validate OpenAPI 3.1 specifications from codebases with oasdiff CI gates.
npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-api-spec
Please help me install this Agent Skill. Skill: hatch3r-api-spec Source: https://github.com/hatch3r/hatch3r/tree/main/skills/hatch3r-api-spec Command: npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-api-spec
It reduces the risk of outdated or incorrect API documentation by turning your codebase into a validated OpenAPI specification with breaking-change protection.
oasdiff breaking-change CI gate to prevent breaking changes to stable endpoints.Ask the AI to scan your repository endpoints and generate an OpenAPI 3.1 spec (openapi.yaml), including schema validation and an oasdiff breaking-change CI gate wired to your stable endpoints policy.
High-intent search queries and answers about installing and using this skill.
Generating an OpenAPI specification from a codebase involves inventorying endpoints, extracting request/response shapes and auth requirements, and producing an OpenAPI 3.1 document with reusable schemas. This process ensures your API documentation accurately reflects your actual codebase.
Yes, you can prevent breaking API changes in CI by wiring an oasdiff breaking-change gate to fail on ERR-level breakages for stable endpoints. This validates schema constraints and ensures controlled evolution across releases.
Inventory-first endpoint mapping extracts methods, paths, parameters, status codes, and auth requirements directly from the codebase to produce accurate API documentation. It ensures your OpenAPI schemas align with real serialized output rather than manual annotations.
Validating schema constraints against runtime serialization requires verifying that generated OpenAPI schemas match actual output through linter-based validation. This ensures schema correctness and detects ambiguities between documented specifications and runtime behavior.
No, you do not need existing API annotations because the generation process inventories endpoints directly from the codebase to extract methods, paths, and request/response shapes. It produces OpenAPI 3.1 documents with grouped tags and matching security schemes automatically.
You should use a breaking-change CI gate when you need consistent API contracts for SDK clients and controlled evolution across releases. It prevents outdated or incorrect API documentation by failing CI on ERR-level breakages to stable endpoints.
CrazyDubyaGenerate OpenAPI 3.0 documentation from API route definitions in code.
JayRHaGenerates Markdown API reference pages and validated OpenAPI 3.1 specifications from routes, controllers and live endpoints.
proffesor-for-testingVerify microservice API providers against consumer-driven Pact contracts in CI/CD pipelines.
ValyntValidate and auto-fix OpenAPI 3.0/3.1 specifications in YAML or JSON.