openapi-workflow
Proactive OpenAPI workflow. Triggers when OpenAPI spec files are modified to validate, regenerate code, and verify builds.
Works with
--- name: openapi-workflow description: Proactive OpenAPI workflow. Triggers when OpenAPI spec files are modified to validate, regenerate code, and verify builds. license: MIT --- # OpenAPI Workflow Skill Automatically runs the OpenAPI workflow when spec files are modified. ## When to Activate This skill should activate when: - Files in `backend/api/*.yaml` are modified - New endpoints are added to OpenAPI spec - Request/response schemas are changed - User asks to add/modify API endpoints ## OpenAPI Spec Location | Type | Path | Purpose | |------|------|---------| | API Spec | `backend/api/openapi.yaml` | Public API definition | ## Workflow Steps ### 1. Validate Spec ```bash python3 scripts/openapi_workflow.py --validate ``` ### 2. Generate Code (All Platforms) ```bash python3 scripts/openapi_workflow.py --codegen ``` This generates: - **Backend (Go)**: `backend/internal/generated/` - **iOS (Swift)**: `mobile/ios/App/Generated/` - **Android (Kotlin)**: `mobile/android/app/src/main/java/.../generated/` - **Web (TypeScript)**: `web/src/generated/` ### 3. Build Verification ```bash python3 scripts/openapi_workflow.py --build ``` ### 4. Full Workflow (All Steps) ```bash python3 scripts/openapi_workflow.py --full ``` ## Critical Rules | Rule | Why | |------|-----| | Define response schemas properly | Inline schemas don't generate reusable types | | Use plural file names | REST convention: `users.yaml` not `user.yaml` | | Always regenerate after spec changes | Generated code must match spec | | Verify ALL platforms build | API changes affect backend + iOS + Android + web | ## Process 1. Detect OpenAPI spec was modified 2. Run validation to catch syntax/semantic errors 3. Regenerate code for all platforms 4. Run build verification 5. Report any failures ## Output Format ``` ## OpenAPI Workflow Results **Spec Modified**: [file path] **Validation**: ✅ Passed / ❌ Failed **Code Generation**: ✅ All platforms / ❌ Failed for [platform] **Build Verification**: ✅ All platforms / ❌ Failed for [platform] [Details of any failures] ``` ## Reference - Script: `scripts/openapi_workflow.py` - Spec: `backend/api/openapi.yaml`
More API Design skills
lark-event
larksuite/cli
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.
lark-contact
larksuite/cli
飞书 / Lark 通讯录:按姓名 / 邮箱解析成 open_id,或按 open_id 反查姓名 / 部门 / 邮箱 / 联系方式 / 个人状态 / 签名,以及按关键词搜索当前用户可见的机器人 / 智能体(agent)。当用户提到一个名字要下一步发消息 / 排日程,或拿到 open_id 想查具体信息时使用。不负责部门树遍历、按部门列员工、组织架构图,这类需求走原生 OpenAPI。
lark-openapi-explorer
larksuite/cli
飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。

