원클릭으로
release-check
Pre-release validation checklist. Use before tagging a version or publishing to PyPI. Manual invocation only.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Pre-release validation checklist. Use before tagging a version or publishing to PyPI. Manual invocation only.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | release-check |
| description | Pre-release validation checklist. Use before tagging a version or publishing to PyPI. Manual invocation only. |
| disable-model-invocation | true |
| allowed-tools | ["Bash(poetry *)","Bash(python *)","Bash(git *)","Read","Grep","Glob"] |
Run every gate. ALL must pass before release.
poetry run pytest tests/ --cov=openclaw_sdk --cov-report=term-missing -x
Gate: 0 failures, 90%+ coverage
poetry run mypy --strict src/openclaw_sdk
Gate: 0 errors
poetry run ruff check src/ tests/ && poetry run black --check src/ tests/
Gate: 0 issues
PYTHONIOENCODING=utf-8 python -m mkdocs build 2>&1
Gate: No broken links or warnings
Check that version matches across:
pyproject.toml → version = "..."CHANGELOG.md → has entry for this versionSTATUS.md → reflects current statesrc/openclaw_sdk/__init__.py → __version__ if presentpoetry build
Gate: Produces .tar.gz and .whl without errors
git status
git log --oneline -5
Gate: Clean working tree, on correct branch
Summarize: PASS/FAIL for each gate, total test count, coverage %, version string.
Build and deploy documentation to GitHub Pages. Verifies the build locally, then triggers the GitHub Actions workflow. Use after docs/code changes to update the live site.
Prepare and publish a new SDK release. Bumps version, runs quality gate, tags, pushes, and triggers PyPI publish. Use with version argument e.g. /prepare-release 2.2.0
Run integration tests against the live OpenClaw gateway at ws://127.0.0.1:18789. Use when verifying SDK changes work against the real gateway.
Find and update documentation after code changes. Use after implementing features, fixing bugs, or changing APIs to keep docs in sync.
Run the full SDK quality gate — pytest, mypy, and ruff. Use after making code changes to verify nothing is broken.