validator-issue
/validator-issue
Collect runtime evidence, draft a structured GitHub issue for a suspected agent-validator bug, present a full preview, and file only after confirmation — unless invoked in auto-file mode.
Step 1: Get the Bug Description and Mode
Check for auto-file mode: If $ARGUMENTS begins with --auto-file , set auto-file mode to on and strip the prefix to get the remaining text as the bug description. Skip the confirmation step (Step 4) when auto-file mode is on.
Get the description:
-
If a non-empty description remains after stripping any
--auto-fileprefix, use it as the bug description and proceed to Step 2. -
If
$ARGUMENTSis empty (or becomes empty after stripping), ask the user:"Please describe the bug you encountered with agent-validator. What happened, what did you expect, and what were you trying to do?"
Wait for their response before continuing.
Step 2: Collect Evidence
Read .validator/config.yml first to resolve log_dir (default: validator_logs if the field is absent or the file doesn't exist).
More from codagent-ai/agent-validator
validator-help
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".
16validator-commit
>-
16validator-check
>-
16validator-skip
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".
16validator-setup
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".
16validator-run
>-
16