메뉴
Publish a prepared release (phase 7). Usage: /publish-release <version>. Requires version argument. Wraps publish-release.sh for deterministic execution.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
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.
Run corpus regression tests against real-world OpenAPI specs. Usage: /corpus-test [short]
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.
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 | publish-release |
| description | Publish a prepared release (phase 7). Usage: /publish-release <version>. Requires version argument. Wraps publish-release.sh for deterministic execution. |
Publish a prepared release to GitHub. This is phase 7 of the release process.
Usage: /publish-release <version> (e.g., /publish-release v1.46.0)
Before running this skill:
/prepare-release <version> to complete phases 1-6.release/notes-<version>.md⚠️ CRITICAL: This skill wraps
publish-release.sh. Do NOT run release commands manually.
If no version is provided, stop and ask the user:
Error: Version argument required.
Usage: /publish-release <version>
Example: /publish-release v1.46.0
If the version doesn't match the vX.Y.Z pattern, reject it:
Error: Version must match vX.Y.Z pattern (e.g., v1.46.0)
Got: <invalid-version>
Use the AskUserQuestion tool to confirm before proceeding:
Ready to publish release **<version>**?
This will:
1. Create and push git tag <version>
2. Trigger goreleaser workflow
3. Wait for draft release with binaries
4. Publish the release (irreversible)
Proceed? [Yes / Cancel]
From the repository root, run:
.claude/scripts/publish-release.sh <version>
The script handles:
.release/notes-<version>.md (fails if missing)gh release edit --draft=falseOn success, report:
✅ Release <version> published successfully!
View release: https://github.com/erraggy/oastools/releases/tag/<version>
The release includes:
- 8 binary assets for all platforms
- Enhanced release notes (from prepare step)
- Homebrew formula will update automatically
On failure, report the error and suggest recovery steps.
gh release create - goreleaser creates the draft