validator-status
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese/validator-status
/validator-status
Show a detailed summary of the most recent validator session.
显示最近一次验证器会话的详细摘要。
Step 1: Run the status script
步骤1:运行状态脚本
bash
agent-validate status 2>&1The script parses the for session-level data (run count, gate results, pass/fail status) and lists all log files with their paths and sizes.
.debug.logbash
agent-validate status 2>&1该脚本会解析文件以获取会话级数据(运行次数、检查门结果、通过/失败状态),并列出所有日志文件及其路径和大小。
.debug.logStep 2: Read failed gate details
步骤2:查看失败检查门的详情
For each gate marked FAIL in the Gate Results table, read the corresponding log files to extract failure details:
- Check failures (e.g., ): Read the matching
check:src:code-healthfile. Check log formats vary by tool (linters, test runners, code health analyzers) — read the file and extract the relevant error/warning output.check_*.log - Review failures (e.g., ): Read the matching
review:.:code-qualityfile(s). These contain structured violation data withreview_*.json,file,line,issue, andpriorityfields.status
Use the file paths from the "Log Files" section of the script output. Match gate IDs to file names: corresponds to , corresponds to .
check:.:lintcheck_._lint.*.logreview:.:code-qualityreview_._code-quality_*.{log,json}对于检查门结果表中标记为FAIL的每个检查门,读取对应的日志文件以提取失败详情:
- 检查失败(例如):读取匹配的
check:src:code-health文件。检查日志格式因工具而异(代码检查器、测试运行器、代码健康分析器)——读取文件并提取相关的错误/警告输出。check_*.log - 评审失败(例如):读取匹配的
review:.:code-quality文件。这些文件包含结构化的违规数据,包含review_*.json、file、line、issue和priority字段。status
使用脚本输出中「日志文件」部分的文件路径。将检查门ID与文件名匹配:对应,对应。
check:.:lintcheck_._lint.*.logreview:.:code-qualityreview_._code-quality_*.{log,json}Step 3: Present the results
步骤3:呈现结果
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)
将脚本的会话摘要与详细的失败信息整合为一份全面的报告:
- 会话概述(状态、迭代次数、时长、已修复/已跳过/失败的数量)
- 检查门结果表
- 对于任何失败的检查门:来自日志文件的具体错误、违规或测试失败信息
- 对于存在违规的评审:列出每一项违规,包含文件、行号、问题、优先级和当前状态(已修复/已跳过/未解决)