菜单
Shows a summary of the most recent validator session for requests such as "show validator status", "summarize last validator run", or "what failed in the last validator session".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Scans the project and configures checks and reviews for Agent Validator for requests such as "set up validator", "configure checks and reviews", or "initialize validator for this repo".
Diagnoses and explains validator behavior from runtime evidence for requests such as "why did validator fail", "explain validator behavior", "diagnose validator logs", or "what went wrong in the validator run".
Advances the validator execution state baseline without running checks for requests such as "skip validator", "advance validator baseline", or "mark current tree as validated without running checks".
Capture noteworthy review violations for the eval framework. Use when validator-run finds review failures — judges violations and saves notable ones to evals/inventory.yml.
Activates only for explicit validator-aware commit requests such as "commit with validator", "run validator then commit", "run checks before commit", or "skip validator and commit". Excludes plain commit requests.
Activates only for explicit checks-only validation requests such as "run validator checks", "checks only", "check without reviews", or validation without AI review. Runs checks without AI reviews.
| name | validator-status |
| description | Shows a summary of the most recent validator session for requests such as "show validator status", "summarize last validator run", or "what failed in the last validator session". |
| disable-model-invocation | false |
| allowed-tools | Bash, Read |
Show a detailed summary of the most recent validator session.
agent-validate status 2>&1
The script parses the .debug.log for session-level data (run count, gate results, pass/fail status) and lists all log files with their paths and sizes.
For each gate marked FAIL in the Gate Results table, read the corresponding log files to extract failure details:
check:src:code-health): Read the matching check_*.log file. Check log formats vary by tool (linters, test runners, code health analyzers) — read the file and extract the relevant error/warning output.review:.:code-quality): Read the matching review_*.json file(s). These contain structured violation data with file, line, issue, priority, and status fields.Use the file paths from the "Log Files" section of the script output. Match gate IDs to file names: check:.:lint corresponds to check_._lint.*.log, review:.:code-quality corresponds to review_._code-quality_*.{log,json}.
Combine the script's session summary with the detailed failure information into a comprehensive report: