菜单
Manage and formalize API contracts from existing endpoints, swagger/JSON, network traffic, or developer interviews into OpenAPI specifications.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | qa-api-contract-curator |
| description | Manage and formalize API contracts from existing endpoints, swagger/JSON, network traffic, or developer interviews into OpenAPI specifications. |
| output_dir | docs/api-contracts |
Manage and formalize API contracts. Detect breaking changes, generate OpenAPI (OAS) specifications, and produce versioning rules. Transform disparate API information into a single, validated, version-controlled contract.
| Source | Description | How to Use |
|---|---|---|
| Existing endpoints | Live API or network traffic capture | Capture requests/responses via HAR, Postman, browser DevTools; infer schema from payloads |
| Swagger/OpenAPI JSON/YAML | Existing spec files | Parse, validate, normalize to OpenAPI 3.x, fill gaps |
| Developer interviews/descriptions | Natural language API descriptions | Extract endpoints, methods, parameters, responses; formalize into OAS |
| Codebase analysis | Express routes, FastAPI endpoints, Spring controllers, etc. | Scan route definitions, decorators, DTOs; derive contract from implementation |
| Change Type | Description | Severity |
|---|---|---|
| Removed endpoints | Path or method no longer exists | Breaking |
| Changed response schemas | Added/removed fields, type changes | Breaking or additive |
| Modified required fields | New required field in request/response | Breaking |
| Authentication changes | New auth requirement, changed scheme | Breaking |
| Parameter changes | Removed/renamed path/query/header params | Breaking |
| Status code changes | Success/error codes removed or redefined | Breaking |
| Additive changes | New optional fields, new endpoints | Non-breaking |
See references/breaking-changes.md for catalog and mitigation strategies.
Can do (autonomous):
Cannot do (requires confirmation):
Will not do (out of scope):
Before delivering an OpenAPI specification:
{} or placeholder types)| Symptom | Likely Cause | Fix |
|---|---|---|
| Missing request/response schemas | Source has no examples | Infer from code DTOs, add placeholder schemas, ask for samples |
| Duplicate paths from multiple sources | Same API documented in different formats | Merge by path+method, reconcile differences, prefer most complete |
| Breaking changes false positives | Optional vs required misinterpreted | Verify required arrays; additive optional changes are non-breaking |
| Auth not documented | Source lacks auth info | Check codebase for middleware, add security at spec or operation level |
| Invalid OpenAPI output | Schema syntax errors | Validate with openapi-generator validate or Swagger Editor |
| Incomplete codebase extraction | Framework not recognized | Add framework-specific patterns to extraction logic; fall back to manual |
references/openapi-structure.md — OpenAPI 3.x specification structure with examplesreferences/breaking-changes.md — Catalog of breaking changes and mitigation strategiesMaster skill coordinating all QA skills through pipeline modes (full-cycle, docs-only, testcases-only, write-tests, report), formalized handoff chains, scheduler rules, and framework/language selection based on project context.
QA project memory with auto-update. Structured log of bugs, decisions, tests, regressions, environments. Automatically updated after every QA task. Archive system with searchable index for large projects. Trigger phrases (EN): "initialize memory", "init qa memory", "find known bug", "search memory", "show what was done", "check regressions", "memory status", "archive memory", "log a bug", "add decision", "memory summary", "what bugs do we know", "update memory", "show test log". Trigger phrases (UA): "ініціалізувати пам'ять", "знайти відомий баг", "пошук у пам'яті", "показати що було зроблено", "перевірити регресії", "статус пам'яті", "архівувати пам'ять", "залогувати баг", "додати рішення", "зведення пам'яті", "які баги відомі", "оновити пам'ять", "показати лог тестів", "що ми вирішили про", "які тестові середовища є".
Analyze OpenAPI/Swagger spec (JSON or YAML) against existing test files and generate an HTML coverage report with QA automation tasks. Use when user provides an OpenAPI spec file and wants to know test coverage status.
Generate accessibility tests for WCAG 2.2 compliance using axe-core, Pa11y, and Lighthouse with automated checks for ARIA patterns, keyboard navigation, color contrast, and screen reader support.
Autonomously explore live web applications using Playwright MCP to collect page structure, form fields, validation rules, API endpoints, and user flows for test case generation.
Generate structured bug reports from test failures with expected/actual results, reproduction steps, evidence, severity/priority, and auto-create GitHub Issues via GitHub MCP with duplicate detection.