Lang Openapi
Lint and codegen OpenAPI and Swagger specs.
Skill metadata
| Source | Bundled (installed by default) |
| Path | skills/software-development/lang-openapi |
| Version | 1.0.0 |
| Author | VibeOS |
| License | MIT |
| Platforms | linux, macos, windows |
Reference: full SKILL.md
The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.
OpenAPI / Swagger Language Pack Skill
Drive OpenAPI / Swagger work with the project index and standard CLI recipes.
LSP hint: yaml-language-server (editor-side when applicable). Zero new core tools.
What this language is (beginner)
Стандарт описания HTTP API. Один openapi.yaml — документация, клиенты и проверки совместимости для сайта/мобилки/партнёров.
Лучше всего для:
- REST/JSON API контракты
- codegen клиентов SDK
- контракт-тесты
- документация API
When to Use
Выбирай этот pack, если:
- есть openapi.yaml / swagger.json
- нужен контракт REST API
- пользователь просит OpenAPI/Swagger
Manifests (автодетект репозитория): openapi.yaml, openapi.yml, openapi.json, swagger.yaml, swagger.yml, swagger.json, api/openapi.yaml, docs/openapi.yaml
Обычно рядом: TypeScript/Go/Python серверы; часто рядом с Docker.
См. также skill choose-language-pack и vibeos language recommend "…".
When NOT to use
- gRPC между сервисами → protobuf
- GraphQL schema → graphql
- только код без спеки → язык бэкенда
Prerequisites
vibeos pack apply lang-openapi --apply
vibeos pack apply project-intelligence --apply
How to Run
vibeos project index build
npx @redocly/cli lint openapi.yaml || npx spectral lint openapi.yaml || true
Quick Reference
| Goal | Command |
|---|---|
| Apply pack | vibeos pack apply lang-openapi --apply |
| Doctor | vibeos language doctor openapi |
| Primary test | npx @redocly/cli lint openapi.yaml |
| Choose guide | skill choose-language-pack |
| Recommend | vibeos language recommend "…" |
Procedure
- Для нового продукта сначала
choose-language-pack/vibeos language recommend. - Work from the project root that matches pack manifests.
- Prefer project-local toolchain already locked in the repo.
- Explain destructive/export/breaking changes; wait for explicit ask.
- Do not invent core tools; stay on
terminal+read_file+ index CLI.
Pitfalls
- Prefer committed openapi.yaml as source of truth.
- Breaking path/schema changes need explicit review.
Verification
vibeos language doctor openapi
vibeos project index status