メニュー
Proactive OpenAPI workflow. Triggers when OpenAPI spec files are modified to validate, regenerate code, and verify builds.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | openapi-workflow |
| description | Proactive OpenAPI workflow. Triggers when OpenAPI spec files are modified to validate, regenerate code, and verify builds. |
Automatically runs the OpenAPI workflow when spec files are modified.
This skill should activate when:
backend/api/*.yaml are modified| Type | Path | Purpose |
|---|---|---|
| API Spec | backend/api/openapi.yaml | Public API definition |
python3 scripts/openapi_workflow.py --validate
python3 scripts/openapi_workflow.py --codegen
This generates:
backend/internal/generated/mobile/ios/App/Generated/mobile/android/app/src/main/java/.../generated/web/src/generated/python3 scripts/openapi_workflow.py --build
python3 scripts/openapi_workflow.py --full
| 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 |
## 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]
scripts/openapi_workflow.pybackend/api/openapi.yamlProactive code quality review. Triggers on significant code changes to check security, performance, architecture, and project patterns.
Capture learnings after tasks. Triggers on task completion, repeated mistakes, retrospective requests, or "what did I learn".
SDLC workflow with MCP tools. Triggers on "start", "implement", "work on", or unclear workflow.
Git workflow management. Triggers when creating branches, preparing PRs, or managing merge decisions.
Proactive security scanning. Triggers when modifying auth, API endpoints, user data, or sensitive operations.
Systematic debugging with 4-phase root cause analysis. Triggers when bugs are reported, errors encountered, or unexpected behavior observed.