菜单
Run agentic-evalkit's offline verification matrix and release gates in order, reporting pass/fail per gate. Use before opening a PR, before tagging a release, or when asked to "run the gates", "verify the release", or "check release readiness".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/tafreeman/agentic-evalkit --skill release-gate命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | release-gate |
| description | Run agentic-evalkit's offline verification matrix and release gates in order, reporting pass/fail per gate. Use before opening a PR, before tagging a release, or when asked to "run the gates", "verify the release", or "check release readiness". |
Single source of truth for the verification every change and release must
pass. CONTRIBUTING.md describes these gates in prose and
.github/workflows/release-gates.yml runs the release subset in CI; this
skill executes them locally, in order, with one command per gate.
Sync the environment once — and never run two gate sequences
concurrently; parallel uv invocations race on .venv:
uv sync --all-groups
Run the offline verification matrix, in order. Stop and report the first failure with its output; do not continue past a red gate:
uv run pytest --cov --cov-report=term-missing
uv run ruff check .
uv run ruff format --check .
uv run mypy
(pytest deselects live-marked tests by default via addopts; the
coverage floor is 80% branch-aware and fails the run by itself.)
For a release, additionally run the offline release gates:
uv run pytest tests/contract/test_dependency_boundary.py tests/contract/test_adrs.py tests/contract/test_public_docs.py -v
uv run mkdocs build --strict
uv run pytest tests/integration/test_clean_wheel.py -v # slow: real wheel + venv
The live Hugging Face gate requires network access and is never part of
the default matrix. Run it explicitly, or dispatch
.github/workflows/live-provider.yml (the only CI workflow allowed to
touch the real network path):
uv run pytest tests/live/test_huggingface_live.py -m live -v
Report results as a table — gate, command, PASS/FAIL — followed by the failing output for any FAIL. A classified transient outage on the live gate is a known issue to document, never something to retry into a false pass.
To run everything unattended in one pass instead of step by step:
bash .claude/skills/release-gate/scripts/run-gates.sh # offline matrix
bash .claude/skills/release-gate/scripts/run-gates.sh --release # + release gates
bash .claude/skills/release-gate/scripts/run-gates.sh --release --live # + network gate
references/gate-commands.md — every gate with what it proves and its
typical failure modes.