release-readiness
Use when preparing to tag, publish, or deploy a genefoundry-router build.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when preparing to tag, publish, or deploy a genefoundry-router build.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when `make ci-local` fails locally or a GitHub Actions run reports a CI failure (format, lint, line-budget, typecheck, or test errors).
Use when reviewing a diff, PR, or change set for correctness and quality before merge or handoff. For a deep security-only pass, use security-review instead.
Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.
Use when reviewing genefoundry-router security before deploy, when touching auth/proxy/logging/limits config, or when answering an infosec/DSB question.
Use when changing the router's authentication or authorization — JWT/OAuth modes, verifiers, resource/audience metadata, the secure-by-default bind guard, or the no-token-passthrough boundary.
Use when adding, removing, enabling/disabling, or reconfiguring a backend in the router's servers.yaml registry (URLs, namespaces, entrypoints, server_name/transform overrides).
| name | release-readiness |
| description | Use when preparing to tag, publish, or deploy a genefoundry-router build. |
Follow AGENTS.md first.
make ci-local; then make docker-build and any docker-*-config validation targets the Makefile exposes.make fleet-probe — confirm every enabled backend is reachable and harvests a non-zero tool set (closes the CI≠prod gap); make list-tools for the namespaced surface.make snapshot-catalog and review; re-pin the drift baseline (make snapshot-baseline) only after reviewing the diff.serverInfo.version framework leak) and hardened container overlays (ports: !reset [], cap-drop, read-only).