Menú
Run corpus regression tests against real-world OpenAPI specs. Usage: /corpus-test [short]
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Prepare a release (phases 1-6). Usage: /prepare-release [version]. If version omitted, infers from conventional commits. Coordinates agents for review, runs prepare-release.sh, then enhances release notes with rich formatting.
Generate test scaffolding for a Go file following oastools conventions. Usage: /gen-test <file.go> [function names...]
Review unpushed commits before pushing for code quality, bugs, security issues, and error handling. Use when preparing to push commits, want pre-push code review, or need to validate changes before pushing. Runs comprehensive analysis using specialized review agents.
Publish a prepared release (phase 7). Usage: /publish-release <version>. Requires version argument. Wraps publish-release.sh for deterministic execution.
Run full validation suite (make check + gopls diagnostics) and report structured pass/fail. Usage: /quality-gate [package...]
Compare two OpenAPI spec versions, highlight breaking changes, and suggest migration steps
| name | corpus-test |
| description | Run corpus regression tests against real-world OpenAPI specs. Usage: /corpus-test [short] |
Run integration tests against the corpus of real-world OpenAPI specifications.
Usage:
/corpus-test — run all corpus tests/corpus-test short — exclude large specs (faster)Use the Glob tool to check for corpus files:
pattern: testdata/corpus/*.{json,yaml,yml}
If no corpus files found, download them:
make corpus-download
Based on the mode argument:
Full mode (default):
make test-corpus
Short mode (argument = "short"):
make test-corpus-short
Capture and analyze the output.
Note: Corpus specs are real-world documents (Plaid, DigitalOcean, GitHub, etc.) that often contain validation errors intentionally. Validation failures are expected — the key metric is whether the fixer resolves them.
For each corpus spec, report:
## Corpus Test Results
| Spec | Parse | Validate | Fix | Notes |
|------|-------|----------|-----|-------|
| petstore.yaml | ✅ | ✅ | ✅ | |
| github-api.json | ✅ | ❌ | ⚠️ | [details] |
| ... | ... | ... | ... | ... |
### Summary
- **Passed**: N/M specs
- **Failed**: [list]
- **New issues**: [list]
If failures are found: