Run any Skill in Manus with one click

$pwd:

openapi-workflow

Name: Openapi Workflow
Author: muyen

// Proactive OpenAPI workflow. Triggers when OpenAPI spec files are modified to validate, regenerate code, and verify builds.

Run Skill in Manus

$ git log --oneline --stat

stars:33

forks:8

updated:January 3, 2026 at 19:11

SKILL.md

readonly

name	openapi-workflow
description	Proactive OpenAPI workflow. Triggers when OpenAPI spec files are modified to validate, regenerate code, and verify builds.

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

python3 scripts/openapi_workflow.py --validate

2. Generate Code (All Platforms)

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

python3 scripts/openapi_workflow.py --build

4. Full Workflow (All Steps)

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

Detect OpenAPI spec was modified
Run validation to catch syntax/semantic errors
Regenerate code for all platforms
Run build verification
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

related-skills.json

same repository

code-review.md

from "muyen/vibe-to-prod"

Proactive code quality review. Triggers on significant code changes to check security, performance, architecture, and project patterns.

2026-01-0333

continuous-improvement.md

from "muyen/vibe-to-prod"

Capture learnings after tasks. Triggers on task completion, repeated mistakes, retrospective requests, or "what did I learn".

2026-01-0333

dev-workflow.md

from "muyen/vibe-to-prod"

SDLC workflow with MCP tools. Triggers on "start", "implement", "work on", or unclear workflow.

2026-01-0333

git-workflow.md

from "muyen/vibe-to-prod"

Git workflow management. Triggers when creating branches, preparing PRs, or managing merge decisions.

2026-01-0333

security-scan.md

from "muyen/vibe-to-prod"

Proactive security scanning. Triggers when modifying auth, API endpoints, user data, or sensitive operations.

2026-01-0333

systematic-debugging.md

from "muyen/vibe-to-prod"

Systematic debugging with 4-phase root cause analysis. Triggers when bugs are reported, errors encountered, or unexpected behavior observed.

2026-01-0333

package.json

"author": "muyen"

"repository": "muyen/vibe-to-prod"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	openapi-workflow
description	Proactive OpenAPI workflow. Triggers when OpenAPI spec files are modified to validate, regenerate code, and verify builds.

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

python3 scripts/openapi_workflow.py --validate

2. Generate Code (All Platforms)

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

python3 scripts/openapi_workflow.py --build

4. Full Workflow (All Steps)

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

Detect OpenAPI spec was modified
Run validation to catch syntax/semantic errors
Regenerate code for all platforms
Run build verification
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

openapi-workflow

OpenAPI Workflow Skill

When to Activate

OpenAPI Spec Location

Workflow Steps

1. Validate Spec

2. Generate Code (All Platforms)

3. Build Verification

4. Full Workflow (All Steps)

Critical Rules

Process

Output Format

Reference

More from this repository

More from this repository

OpenAPI Workflow Skill

When to Activate

OpenAPI Spec Location

Workflow Steps

1. Validate Spec

2. Generate Code (All Platforms)

3. Build Verification

4. Full Workflow (All Steps)

Critical Rules

Process

Output Format

Reference