Lint OpenAPI specs with Spectral using a .spectral.yml configuration.
npx skills add https://github.com/zerobias-org/module --skill spectral-linting
Please help me install this Agent Skill. Skill: spectral-linting Source: https://github.com/zerobias-org/module/tree/main/.claude/skills/spectral-linting Command: npx skills add https://github.com/zerobias-org/module --skill spectral-linting
OpenAPI specs often drift or contain errors that slip into production, causing integration issues and slow down development. This Skill provides a standardized Spectral-based linting setup to catch common OpenAPI mistakes before merge and promote consistent API documentation.
Install Spectral and run lint on your OpenAPI spec using the spectral-cli tool.
High-intent search queries and answers about installing and using this skill.
You can lint OpenAPI specs in CI pipelines using Spectral to catch API errors before merge and promote consistent API documentation across projects. This setup requires a .spectral.yml configuration file and a basic OpenAPI document to begin automated linting.
Spectral linting catches common OpenAPI drift and errors before production, enforcing checks like operationId presence, 2xx responses, tag definitions, and valid schemas to reduce integration issues and regressions.
To start linting an OpenAPI document with Spectral, you need a .spectral.yml file in your project root and a basic OpenAPI document. You then install Spectral and run the lint using the spectral-cli tool.
Yes, you can use Spectral to automatically lint OpenAPI specs in pull requests. This Skill provides CI-friendly guidance to integrate Spectral into your pipelines, ensuring API quality checks run automatically before merges.
Spectral provides a standardized linting setup with a recommended baseline configuration for critical and warning rules, specifically designed to prevent OpenAPI spec drift and catch integration issues early in development.
Yes, Spectral supports a ready-made configuration with a recommended baseline for critical and warning rules, providing clear guidance specifically designed to onboard new API teams and enforce consistent quality checks.
AhamSammichGenerate an XML app specification document from a codebase.
srivtxAutomate code review for local changes and GitHub pull requests.
LiorCohenDefine OpenAPI contract standards and generate TypeScript types from specs.
ValyntValidate and auto-fix OpenAPI 3.0/3.1 specifications in YAML or JSON.
