with one click
release-check
Verify a release candidate before publishing it.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Verify a release candidate before publishing it.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create a bounded, read-only investigation from normalized Codex or Claude Code Run Records, optionally inspect explicit AET Proof and Freshness records, and export a Portable Evidence Bundle for an independent reviewer.
Run a bounded AET check of Agent instructions, Skills, verification contracts, and dangerous authority. Use only when the user explicitly invokes /aet-check or asks for this AET Quick check.
Deterministically check whether an AET proof still applies to the current workspace. Use only for an explicit /aet-fresh request.
Execute one explicit verification command and record a minimal hash-bound AET proof receipt. Use only when the user explicitly invokes /aet-proof or asks AET to prove a command ran.
Investigate whether an AI coding change matches the user's task and whether cross-module changes are necessary. Use only for an explicit /aet-scope request.
Compatibility entrypoint for AET Quick and advanced AET Lab workflows. Prefer the four dedicated Quick Skills for daily work; use this Skill only when the user explicitly asks for legacy CLI or Lab capabilities.
| name | release-check |
| description | Verify a release candidate before publishing it. |
Run python scripts/check_release.py and inspect the exit status before saying
that the release is ready. Generated evidence is named evidence_YYYYMMDD.json.
See the detailed procedure.