/validator-status
Show a detailed summary of the most recent validator session.
Step 1: Run the status script
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.
Step 2: Read failed gate details
For each gate marked FAIL in the Gate Results table, read the corresponding log files to extract failure details:
- Check failures (e.g.,
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 failures (e.g.,
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}.
Step 3: Present the results
Combine the script's session summary with the detailed failure information into a comprehensive report:
- Session overview (status, iterations, duration, fixed/skipped/failed counts)
- Gate results table
- For any failed gates: the specific errors, violations, or test failures from the log files
- For reviews with violations: list each violation with file, line, issue, priority, and current status (fixed/skipped/outstanding)
1---2name: validator-status3description: 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".4---56# /validator-status7Show a detailed summary of the most recent validator session.89## Step 1: Run the status script1011```bash12agent-validate status 2>&113```1415The 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.1617## Step 2: Read failed gate details1819For each gate marked **FAIL** in the Gate Results table, read the corresponding log files to extract failure details:2021- **Check failures** (e.g., `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.22- **Review failures** (e.g., `review:.:code-quality`): Read the matching `review_*.json` file(s). These contain structured violation data with `file`, `line`, `issue`, `priority`, and `status` fields.2324Use 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}`.2526## Step 3: Present the results2728Combine the script's session summary with the detailed failure information into a comprehensive report:29301. Session overview (status, iterations, duration, fixed/skipped/failed counts)312. Gate results table323. For any failed gates: the specific errors, violations, or test failures from the log files334. For reviews with violations: list each violation with file, line, issue, priority, and current status (fixed/skipped/outstanding)
codagent-ai